From: Peter Zijlstra <peterz@infradead.org>
To: Zeng Heng <zengheng4@huawei.com>
Cc: mingo@redhat.com, bp@alien8.de, jroedel@suse.de, vbabka@suse.cz,
hpa@zytor.com, tglx@linutronix.de, eric.devolder@oracle.com,
bhe@redhat.com, tiwai@suse.de, keescook@chromium.org,
dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
x86@kernel.org, liwei391@huawei.com, xiexiuqi@huawei.com
Subject: Re: [PATCH v3] x86/kdump: Handle blocked NMIs interrupt to avoid kdump crashes
Date: Tue, 14 Feb 2023 10:49:07 +0100 [thread overview]
Message-ID: <Y+tZE8ixmlIDYrOu@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <e57ba121-5bcc-e63b-691d-3e3d998e9e48@huawei.com>
On Tue, Feb 14, 2023 at 05:30:46PM +0800, Zeng Heng wrote:
> > I never remember the shutdown paths -- do we force wipe the PMU
> > registers somewhere before this?
>
> I have checked the panic process, and there is no wipe operation for PMU
> registers,
>
> which causes the watchdog bites.
>
> Do you mean we should directly disable PMU registers instead of calling
> `iret_to_self` to
>
> consume blocked NMI interrupts ?
If you don't wipe the PMU, there will be many and continuous NMIs, a
single IRET-to-SELF isn't going to safe you.
Anyway, I had a bit of a grep around and I find we have:
kernel/events/core.c: register_reboot_notifier(&perf_reboot_notifier);
which should end up killing all the PMU activity. Somewhere around there
there's also a CONFIG_KEXEC_CORE ifdef, so I'm thinking it gets called
on the panic->crash-kernel path too?
If not, someone should look at doing something there.
next prev parent reply other threads:[~2023-02-14 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 1:40 [PATCH v3] x86/kdump: Handle blocked NMIs interrupt to avoid kdump crashes Zeng Heng
2023-02-02 9:09 ` Peter Zijlstra
2023-02-14 9:30 ` Zeng Heng
2023-02-14 9:49 ` Peter Zijlstra [this message]
2023-02-15 1:01 ` Baoquan He
2023-02-15 3:05 ` Zeng Heng
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=Y+tZE8ixmlIDYrOu@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eric.devolder@oracle.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=vbabka@suse.cz \
--cc=x86@kernel.org \
--cc=xiexiuqi@huawei.com \
--cc=zengheng4@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