From: Andy Lutomirski <luto@kernel.org>
To: Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Lai Jiangshan <laijs@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC PATCH 2/4] x86/entry/nmi: Use normal idtentry macro for NMI from userspace
Date: Thu, 3 Jun 2021 10:36:19 -0700 [thread overview]
Message-ID: <9bc8ec45-c87f-ad38-a028-0df50a0c4516@kernel.org> (raw)
In-Reply-To: <20210601065217.23540-3-jiangshanlai@gmail.com>
On 5/31/21 11:52 PM, Lai Jiangshan wrote:
> From: Lai Jiangshan <laijs@linux.alibaba.com>
>
> Before tglx made huge refactor on entry code, high level code is called
> from ASM code including idtentry exit path which might reopen IRQ,
> reschedule, do signal among other works and made normal entry path not
> suitable for userspace NMI entry. So when the commit 9b6e6a8334d56
> ("x86/nmi/64: Switch stacks on userspace NMI entry") added special code
> for userspace NMI entry, it didn't use normal entry code.
>
> After the said refactor on entry code, high level code was moved into
> C code, and the idtentry macros are really low level and fit for
> userspace NMI entry after it switches to entry stack, so this
> patch uses idtentry_body macro for NMI from userspace.
>
> Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
> ---
> arch/x86/entry/entry_64.S | 42 ++++++---------------------------------
> 1 file changed, 6 insertions(+), 36 deletions(-)
>
> diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S
> index 4190e668f346..f54e06139d4b 100644
> --- a/arch/x86/entry/entry_64.S
> +++ b/arch/x86/entry/entry_64.S
> @@ -1113,11 +1113,7 @@ SYM_CODE_START(asm_exc_nmi)
> jz .Lnmi_from_kernel
>
> /*
> - * NMI from user mode. We need to run on the thread stack, but we
> - * can't go through the normal entry paths: NMIs are masked, and
> - * we don't want to enable interrupts, because then we'll end
> - * up in an awkward situation in which IRQs are on but NMIs
> - * are off.
> + * NMI from user mode. We need to run on the thread stack.
This comment is IMO still important, but I think you're right that it no
longer matters in the asm. Could you relocate the comment to the
appropriate place in the C code so that a future cleanup doesn't mess up
the C path?
Thanks,
Andy
next prev parent reply other threads:[~2021-06-03 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 6:52 [RFC PATCH 0/4] x86/entry/nmi: solidify userspace NMI entry Lai Jiangshan
2021-06-01 6:52 ` [RFC PATCH 1/4] x86/entry/nmi: Switch to the entry stack before switching to the thread stack Lai Jiangshan
2021-06-01 17:05 ` Steven Rostedt
2021-06-02 0:09 ` Lai Jiangshan
2021-06-02 0:16 ` Lai Jiangshan
2021-06-19 22:51 ` Thomas Gleixner
2021-06-20 3:13 ` Andy Lutomirski
2021-06-20 11:23 ` Thomas Gleixner
2021-06-25 10:40 ` Peter Zijlstra
2021-06-25 11:00 ` Peter Zijlstra
2021-06-26 7:03 ` Thomas Gleixner
2021-06-26 8:28 ` Peter Zijlstra
2021-06-01 6:52 ` [RFC PATCH 2/4] x86/entry/nmi: Use normal idtentry macro for NMI from userspace Lai Jiangshan
2021-06-03 17:36 ` Andy Lutomirski [this message]
2021-06-01 6:52 ` [RFC PATCH 3/4] x86/entry: Remove parameter rdx from macro PUSH_AND_CLEAR_REGS and PUSH_REGS Lai Jiangshan
2021-06-01 6:52 ` [RFC PATCH 4/4] x86/entry/nmi: unmask NMIs on userspace NMI when entry debugging Lai Jiangshan
2021-06-03 17:38 ` Andy Lutomirski
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=9bc8ec45-c87f-ad38-a028-0df50a0c4516@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jiangshanlai@gmail.com \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).