From: Ingo Molnar <mingo@kernel.org>
To: Zeng Heng <zengheng4@huawei.com>
Cc: michael.roth@amd.com, bp@alien8.de, hpa@zytor.com,
tglx@linutronix.de, sathyanarayanan.kuppuswamy@linux.intel.com,
kirill.shutemov@linux.intel.com, jroedel@suse.de,
keescook@chromium.org, mingo@redhat.com,
dave.hansen@linux.intel.com, brijesh.singh@amd.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
liwei391@huawei.com
Subject: Re: [PATCH] x86/boot/compressed: Register NMI handler in EFI boot loader
Date: Tue, 10 Jan 2023 11:59:51 +0100 [thread overview]
Message-ID: <Y71FJ+G0NGQe3Ppq@gmail.com> (raw)
In-Reply-To: <20230110102745.2514694-1-zengheng4@huawei.com>
* Zeng Heng <zengheng4@huawei.com> wrote:
> +void do_boot_nmi_fault(struct pt_regs *regs, unsigned long error_code)
> +{
> + /* ignore */
> +}
> diff --git a/arch/x86/boot/compressed/idt_64.c b/arch/x86/boot/compressed/idt_64.c
> index 6debb816e83d..b169c9728d52 100644
> --- a/arch/x86/boot/compressed/idt_64.c
> +++ b/arch/x86/boot/compressed/idt_64.c
> @@ -60,6 +60,7 @@ void load_stage2_idt(void)
> {
> boot_idt_desc.address = (unsigned long)boot_idt;
>
> + set_idt_entry(X86_TRAP_NMI, boot_nmi_fault);
> set_idt_entry(X86_TRAP_PF, boot_page_fault);
So it's a bit sad to install a dummy handler that does nothing, while
something clearly sent an NMI and expects an intelligent reaction - OTOH
the unexpected NMIs from from watchdog during a kdump clearly make things
worse by crashing the bootup.
Anyway, I cannot think of a better response here that the boot loading code
could do either, so I've applied your fix to tip:x86/boot.
Thanks,
Ingo
next prev parent reply other threads:[~2023-01-10 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:27 Zeng Heng
2023-01-10 10:59 ` Ingo Molnar [this message]
2023-01-10 12:01 ` [PATCH -v2] x86/boot/compressed: Register dummy NMI handler in EFI boot loader, to avoid kdump crashes Ingo Molnar
2023-01-10 12:11 ` Borislav Petkov
2023-01-10 12:17 ` Borislav Petkov
2023-01-10 12:34 ` Ingo Molnar
2023-01-10 12:46 ` Borislav Petkov
2023-01-10 12:50 ` Zeng Heng
2023-01-10 12:32 ` Zeng Heng
2023-01-10 12:57 ` Borislav Petkov
2023-01-10 13:42 ` Zeng Heng
2023-01-10 16:09 ` Borislav Petkov
2023-01-12 2:07 ` Zeng Heng
2023-01-10 14:53 ` Borislav Petkov
2023-01-11 3:46 ` Zeng Heng
2023-01-10 14:06 ` Zeng Heng
2023-01-10 11:41 ` [tip: x86/boot] " tip-bot2 for 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=Y71FJ+G0NGQe3Ppq@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®