[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9dfd8510-91e5-40c4-a3ec-6f70667fc366@huawei.com>
Date: Mon, 11 Aug 2025 20:51:37 +0800
From: Yipeng Zou <zouyipeng@...wei.com>
To: Thomas Gleixner <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<peterz@...radead.org>, <sohil.mehta@...el.com>, <rui.zhang@...el.com>,
<arnd@...db.de>, <yuntao.wang@...ux.dev>, <linux-kernel@...r.kernel.org>
Subject: Re: [BUG REPORT] x86/apic: CPU Hang in x86 VM During Kdump
在 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
Powered by blists - more mailing lists