From: Steven Rostedt <rostedt@goodmis.org>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: linux-trace-devel@vger.kernel.org, mhiramat@kernel.org,
Ross Zwisler <zwisler@google.com>
Subject: Re: [PATCH v2] tracing: Dump instance traces into dmesg on ftrace_dump_on_oops
Date: Thu, 10 Nov 2022 00:47:05 -0500 [thread overview]
Message-ID: <20221110004705.50a8a147@rorschach.local.home> (raw)
In-Reply-To: <20221110031019.3005130-1-joel@joelfernandes.org>
On Thu, 10 Nov 2022 03:10:19 +0000
"Joel Fernandes (Google)" <joel@joelfernandes.org> wrote:
> Currently ftrace only dumps the global trace buffer on an OOPs. For
> debugging a production usecase, I'd like to dump instance traces as
> well, into the kernel logs. The reason is we cannot use the global trace
> buffer as it may be used for other purposes.
>
> This patch adds support for dumping the trace buffer instances along
> with the global trace buffer.
>
> The instance traces are dumped first, and then the global trace buffer.
>
> Cc: Ross Zwisler <zwisler@google.com>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> ---
>
Please send kernel related patches to LKML and to
linux-trace-kernel@vger.kernel.org.
linux-trace-devel is for user space tooling.
I had a patch to update MAINTAINERS, but it seems that it was never
applied. :-/
Thanks!
-- Steve
prev parent reply other threads:[~2022-11-10 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 3:10 [PATCH v2] tracing: Dump instance traces into dmesg on ftrace_dump_on_oops Joel Fernandes (Google)
2022-11-10 5:47 ` Steven Rostedt [this message]
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=20221110004705.50a8a147@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=joel@joelfernandes.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).