[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB608345327C015187C13A23D3FCED2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 16 May 2024 20:03:18 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Williams, Dan J" <dan.j.williams@...el.com>, Borislav Petkov
<bp@...en8.de>
CC: "Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>, "Rafael J.
Wysocki" <rafael@...nel.org>, Len Brown <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"rostedt@...dmis.org" <rostedt@...dmis.org>
Subject: RE: [RFC PATCH v2 3/3] ACPI: extlog: Make print_extlog_rcd() log
unconditionally
> Given that is has not kept pace the next question is whether the kernel
> should bother to maintain the contract => "if nothing is watching
> tracepoints some subset (all?) hardware error messages will be reflected
> to the kernel log".
I'm with you for corrected & recoverable errors. The console is a terrible
place for those logs.
But it's handy to have fatal errors go to the console. They may make it out to a
serial port, or be stashed in pstore for later retrieval. Trace event logs that
are handled by some user level daemon are just going to disappear in a
puff of reset smoke.
-Tony
Powered by blists - more mailing lists