From: John Ogness <john.ogness@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] printk's sync mode for ftrace_dump()
Date: Fri, 29 Oct 2021 13:18:33 +0206 [thread overview]
Message-ID: <87y26c9ja6.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20211029102603.4qp4g5bzuydrbkrx@linutronix.de>
On 2021-10-29, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> ftrace_dump() is used for instance by alt-sysrq-z / sysrq_ftrace_dump().
> The function itself dumps the whole trace buffer in an irq-off section so
> no need to talk about max latencies unless this is going to change.
>
> The output on the serial is more or less brief and starts with
> "** 397774 printk messages dropped **"
> and so I do see only the end of it. Might be okay.
> Any reason not to use the sync mode + atomic console while ftrace_dump()
> is in progress?
Since latencies are not a concern, I see no reason not to use
sync+atomic.
However, it does put us into the situation of beginning to define
non-emergency scenarios where sync+atomic is used. That rabbit hole
might go quite deep. I wonder if it might be better to introduce a new
sysrq to toggle sync mode.
John
next prev parent reply other threads:[~2021-10-29 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 10:26 [RFC] printk's sync mode for ftrace_dump() Sebastian Andrzej Siewior
2021-10-29 11:12 ` John Ogness [this message]
2021-11-02 12:20 ` Sebastian Andrzej Siewior
2021-11-02 12:45 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y26c9ja6.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox