[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0ib+Xg_tXb9yURFt91kJ9cFT48KzLaOjJ94gefRHCMbag@mail.gmail.com>
Date: Thu, 5 Jan 2023 15:55:33 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Joel Fernandes <joel@...lfernandes.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>,
linux-acpi@...r.kernel.org, Len Brown <lenb@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Brian Norris <briannorris@...omium.org>,
Ross Zwisler <zwisler@...gle.com>,
Ching-lin Yu <chinglinyu@...gle.com>
Subject: Re: [RFC][PATCH] ACPI: tracing: Have ACPI debug go to tracing ring buffer
On Wed, Jan 4, 2023 at 10:39 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Fri, 30 Dec 2022 16:52:36 +0100
> "Rafael J. Wysocki" <rafael@...nel.org> wrote:
>
> > Personally, I would use a command line option to control the behavior
> > and the Kconfig option to provide its default value.
> >
>
> I can add that.
>
> > This way it can be flipped without rebuilding the kernel if need be.
> >
> > I would also make the ACPI debug output go into the trace buffer so
> > long as the Kconfig option is not changed or the command line option
> > is not flipped.
>
> Not sure what you mean by the above? You mean to make going to both as the
> default?
No, just send them to the trace buffer alone unless specifically told
to printk() them.
Powered by blists - more mailing lists