[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241230121009.GDZ3KNoe0-hUwQDLG7@fat_crate.local>
Date: Mon, 30 Dec 2024 13:10:09 +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 07:40:18PM +0800, Feng Tang wrote:
> Still we may need to honor the user setting, say if user specifically set
> "panic=XXX" in the cmdline, we should detect that case and skip overwritting
> the panic_timeout?
So the user has set panic timeout to something, machine encounters a hw error
which you want to log/report earlier but user's panic setting prevents you
from doing that.
So what do you do?
What has higher prio?
I guess we're something like this:
https://youtu.be/gLFQystE8vU?t=71
:-P
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists