From: John Ogness <john.ogness@linutronix.de>
To: takakura@valinux.co.jp, pmladek@suse.com, rostedt@goodmis.org,
senozhatsky@chromium.org, akpm@linux-foundation.org,
bhe@redhat.com, lukas@wunner.de, wangkefeng.wang@huawei.com,
ubizjak@gmail.com, feng.tang@intel.com, j.granados@samsung.com,
stephen.s.brennan@oracle.com
Cc: linux-kernel@vger.kernel.org, nishimura@valinux.co.jp,
taka@valinux.co.jp, Ryo Takakura <takakura@valinux.co.jp>
Subject: Re: [PATCH v2 1/2] Handle flushing of CPU backtraces during panic
Date: Mon, 05 Aug 2024 16:10:05 +0206 [thread overview]
Message-ID: <87v80f2hii.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20240803081230.223512-1-takakura@valinux.co.jp>
On 2024-08-03, takakura@valinux.co.jp wrote:
> From: Ryo Takakura <takakura@valinux.co.jp>
>
> After panic, non-panicked CPU's has been unable to flush ringbuffer
> while they can still write into it. This can affect CPU backtrace
> triggered in panic only able to write into ringbuffer incapable of
> flushing them.
Right now, they cannot write to it. If you apply your second patch
before this one, then the above statement is true.
Perhaps the ordering of the two patches should be reversed?
Either way, for the series:
Reviewed-by: John Ogness <john.ogness@linutronix.de>
next prev parent reply other threads:[~2024-08-05 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 8:04 [PATCH v2 0/2] printk: CPU backtrace not printing on panic takakura
2024-08-03 8:12 ` [PATCH v2 1/2] Handle flushing of CPU backtraces during panic takakura
2024-08-05 13:49 ` Petr Mladek
2024-08-05 14:08 ` John Ogness
2024-08-07 8:56 ` takakura
2024-08-05 14:04 ` John Ogness [this message]
2024-08-07 8:59 ` takakura
2024-08-03 8:16 ` [PATCH v2 2/2] Allow cpu backtraces to be written into ringbuffer " takakura
2024-08-05 13:51 ` Petr Mladek
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=87v80f2hii.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=feng.tang@intel.com \
--cc=j.granados@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nishimura@valinux.co.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stephen.s.brennan@oracle.com \
--cc=taka@valinux.co.jp \
--cc=takakura@valinux.co.jp \
--cc=ubizjak@gmail.com \
--cc=wangkefeng.wang@huawei.com \
/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