[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240214102310.7ba53f3a@gandalf.local.home>
Date: Wed, 14 Feb 2024 10:23:10 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc: Ira Weiny <ira.weiny@...el.com>, "Rafael J. Wysocki"
<rafael@...nel.org>, Dan Williams <dan.j.williams@...el.com>, Smita
Koralahalli <Smita.KoralahalliChannabasappa@....com>,
<linux-acpi@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Dan Carpenter <dan.carpenter@...aro.org>,
"Masami Hiramatsu" <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, <linux-trace-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] acpi/ghes: Prevent sleeping with spinlock held
On Wed, 14 Feb 2024 12:11:53 +0000
Jonathan Cameron <Jonathan.Cameron@...wei.com> wrote:
> So I'm thinking this is a won't fix - wait for the printk rework to land and
> assume this will be resolved as well?
That pretty much sums up what I was about to say ;-)
tp_printk is more of a hack and not to be used sparingly. With the right
trace events it can hang the machine.
So, you can use your internal patch locally, but I would recommend waiting
for the new printk changes to land. I'm really hoping that will be soon!
-- Steve
Powered by blists - more mailing lists