From: John Ogness <john.ogness@linutronix.de>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>
Cc: Feng Tang <feng.tang@linux.alibaba.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH] panic: remove redundant panic-cpu backtrace
Date: Thu, 31 Jul 2025 09:15:02 +0206 [thread overview]
Message-ID: <84seichm5t.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20250731030314.3818040-1-senozhatsky@chromium.org>
On 2025-07-31, Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> SYS_INFO_ALL_CPU_BT sends NMI backtrace request to
> all CPUs, which dumps an extra backtrace on panic CPU.
Isn't this only true if CONFIG_DEBUG_BUGVERBOSE=y?
Also, the information is not the same. trigger_all_cpu_backtrace() will
also dump the registers. For CONFIG_DEBUG_BUGVERBOSE=y on the panic CPU,
only the stack is dumped.
John Ogness
next prev parent reply other threads:[~2025-07-31 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 3:02 Sergey Senozhatsky
2025-07-31 7:09 ` John Ogness [this message]
2025-07-31 7:32 ` Sergey Senozhatsky
2025-07-31 7:45 ` John Ogness
2025-07-31 9:51 ` Sergey Senozhatsky
2025-08-12 13:03 ` Petr Mladek
2025-08-13 6:36 ` Sergey Senozhatsky
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=84seichm5t.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
/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
all inboxes | Powered by JetHome®