From: Waiman Long <llong@redhat.com>
To: Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2] x86/nmi: Add an emergency handler in nmi_desc & use it in nmi_shootdown_cpus()
Date: Tue, 3 Dec 2024 20:39:45 -0500 [thread overview]
Message-ID: <0467ac99-dd3d-410a-8326-df4396d0cabb@redhat.com> (raw)
In-Reply-To: <e63226d5a0e3e2c942202972c099617aee999c1a.camel@surriel.com>
On 12/3/24 8:00 PM, Rik van Riel wrote:
> On Tue, 2024-12-03 at 10:07 -0500, Waiman Long wrote:
>> Another way to fix this problem while allowing panic() calls from
>> NMI context is by adding a new emergency NMI handler to the nmi_desc
>> structure and provide a new set_emergency_nmi_handler() helper to
>> atomically set crash_nmi_callback() in any context. The new emergency
>> handler will be invoked first before other handlers in the linked
>> list. That will eliminate the need to take any lock and serve the
>> panic
>> in NMI use case.
>>
>> Signed-off-by: Waiman Long <longman@redhat.com>
> I've seen that panic come by a number of times, but
> never came up with a good fix.
>
> Your idea certainly looks like it should work, and
> avoid all the issues along the way.
>
> Acked-by: Rik van Riel <riel@surriel.com>
Thanks for the review.
Cheers,
Longman
next prev parent reply other threads:[~2024-12-04 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 15:07 Waiman Long
2024-12-04 1:00 ` Rik van Riel
2024-12-04 1:39 ` Waiman Long [this message]
2024-12-04 7:58 ` kernel test robot
2024-12-04 13:10 ` Thomas Gleixner
2024-12-04 17:23 ` Waiman Long
2024-12-04 18:03 ` Thomas Gleixner
2024-12-04 19:28 ` Waiman Long
2024-12-05 4:01 ` Waiman Long
2024-12-05 13:12 ` Thomas Gleixner
[not found] ` <1166fd72-8a4a-489f-9de5-7c06b70b0ad4@redhat.com>
2024-12-05 18:17 ` Thomas Gleixner
2024-12-06 4:16 ` Waiman Long
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=0467ac99-dd3d-410a-8326-df4396d0cabb@redhat.com \
--to=llong@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®