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: Mon, 11 Aug 2025 20:51:37 +0800 [thread overview]
Message-ID: <9dfd8510-91e5-40c4-a3ec-6f70667fc366@huawei.com> (raw)
In-Reply-To: <87a54mkccu.ffs@tglx>
在 2025/7/30 3:48, Thomas Gleixner 写道:
> On Tue, Jul 29 2025 at 21:35, Yipeng Zou wrote:
>> 在 2025/7/29 16:53, Thomas Gleixner 写道:
>>> On Sun, Jul 27 2025 at 22:01, Thomas Gleixner wrote:
>>> 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.
> It's trivial enough to enforce that, no?
Hi Thomas:
Sorry for delay - after resolving a few environmental issues,
anyway, it works.
All previously failed test cases are now passing.
I also think this solution is reasonable.
--
Regards,
Yipeng Zou
prev parent reply other threads:[~2025-08-11 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:33 [BUG REPORT] x86/apic: CPU Hang in x86 VM During Kdump 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
2025-07-29 19:48 ` Thomas Gleixner
2025-08-11 12:51 ` Yipeng Zou [this message]
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=9dfd8510-91e5-40c4-a3ec-6f70667fc366@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;
as well as URLs for NNTP newsgroup(s).