[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241230132403.GEZ3Ke8zm7HxSv84pA@fat_crate.local>
Date: Mon, 30 Dec 2024 14:24:03 +0100
From: Borislav Petkov <bp@...en8.de>
To: Feng Tang <feng.tang@...ux.alibaba.com>
Cc: "Huang, Ying" <ying.huang@...ux.alibaba.com>, rafael@...nel.org,
Len Brown <lenb@...nel.org>, James Morse <james.morse@....com>,
Tony Luck <tony.luck@...el.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, Ira Weiny <ira.weiny@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] acpi/ghes: Make ghes_panic_timeout adjustable as a
parameter
On Mon, Dec 30, 2024 at 09:04:11PM +0800, Feng Tang wrote:
> As per kernel config, most ARCH has 'panic_timeout' as 0 by default, so
> need to set the kcmdline. For the case in my commit log, where user had
> clear requirement for not-reboot and wait, the manually set 'panic=0'
> should take priority here?
I think so.
I'm not convinced that lets-log-the-hw-error-faster should override the panic
timeout setting but I'm open to real-life example scenarios...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists