mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yipeng Zou <zouyipeng@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>, <mingo@redhat.com>,
	<bp@alien8.de>, <dave.hansen@linux.intel.com>, <x86@kernel.org>,
	<hpa@zytor.com>, <peterz@infradead.org>, <sohil.mehta@intel.com>,
	<rui.zhang@intel.com>, <arnd@arndb.de>, <yuntao.wang@linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [BUG REPORT] x86/apic: CPU Hang in x86 VM During Kdump
Date: Tue, 29 Jul 2025 21:35:29 +0800	[thread overview]
Message-ID: <4426d19d-7f7e-411b-8573-36b8990e5d9a@huawei.com> (raw)
In-Reply-To: <87tt2vnzsv.ffs@tglx>


在 2025/7/29 16:53, Thomas Gleixner 写道:
> On Sun, Jul 27 2025 at 22:01, Thomas Gleixner wrote:
>
> But looking even deeper. machine_crash_shutdown() does not end up in
> stop_other_cpus() at all. It immediately uses the NMI shutdown. There
> are still a few inconsistencies in that code, but they are not really
> critical.
>
> So the actual scenario is:
>
> CPU0			  CPU2
> ========================  ======================
> reboot			  Panic
> machine shutdown	  Kdump
> 			  machine_crash_shutdown()
> stop other cpus
> send_IPIs(REBOOT)	  --> REBOOT vector becomes pending in IRR
> wait timeout
>                            send NMI stop
> NMI -> CPU stop
>                            jump to crash kernel
>
> So the patch I gave you should handle the reboot vector pending in IRR
> gracefully. Can you please give it a try?

Hi Thomas:

     Thanks for your time!

     Indeed, It invokes kdump_nmi_shootdown_cpus() and uses the NMI 
shutdown.

     I started the test run today, but this is a low-probability to hit 
this path, might take a while.

-- 
Regards,
Yipeng Zou


  reply	other threads:[~2025-07-29 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04  8:33 Yipeng Zou
2025-07-26  9:50 ` Yipeng Zou
2025-07-27 12:39   ` Thomas Gleixner
2025-07-27 20:01 ` Thomas Gleixner
2025-07-29  8:53   ` Thomas Gleixner
2025-07-29 13:35     ` Yipeng Zou [this message]
2025-07-29 19:48       ` Thomas Gleixner
2025-08-11 12:51         ` Yipeng Zou

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=4426d19d-7f7e-411b-8573-36b8990e5d9a@huawei.com \
    --to=zouyipeng@huawei.com \
    --cc=arnd@arndb.de \
    --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=rui.zhang@intel.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yuntao.wang@linux.dev \
    /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®