From: Steven Rostedt <rostedt@goodmis.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Brian Norris <briannorris@chromium.org>,
Ross Zwisler <zwisler@google.com>,
Ching-lin Yu <chinglinyu@google.com>
Subject: Re: [RFC][PATCH] ACPI: tracing: Have ACPI debug go to tracing ring buffer
Date: Wed, 4 Jan 2023 16:39:13 -0500 [thread overview]
Message-ID: <20230104163913.7b13cd68@gandalf.local.home> (raw)
In-Reply-To: <CAJZ5v0iNdLyOpAxsCTTq-zqRfWDrJ5_c2DUcJYE5ZFn7u+2qdQ@mail.gmail.com>
On Fri, 30 Dec 2022 16:52:36 +0100
"Rafael J. Wysocki" <rafael@kernel.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?
-- Steve
next prev parent reply other threads:[~2023-01-04 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 4:31 Steven Rostedt
2022-12-15 18:45 ` Joel Fernandes
2022-12-15 19:11 ` Steven Rostedt
2022-12-15 19:52 ` Joel Fernandes
2022-12-15 20:13 ` Steven Rostedt
2022-12-30 15:52 ` Rafael J. Wysocki
2023-01-04 21:39 ` Steven Rostedt [this message]
2023-01-05 14:55 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230104163913.7b13cd68@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=briannorris@chromium.org \
--cc=chinglinyu@google.com \
--cc=joel@joelfernandes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rafael@kernel.org \
--cc=zwisler@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®