From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Huang Yiwei <quic_hyiwei@quicinc.com>,
mhiramat@kernel.org, mark.rutland@arm.com, mcgrof@kernel.org,
keescook@chromium.org, j.granados@samsung.com,
mathieu.desnoyers@efficios.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
quic_bjorande@quicinc.com, quic_tsoni@quicinc.com,
quic_satyap@quicinc.com, quic_aiquny@quicinc.com,
kernel@quicinc.com, Ross Zwisler <zwisler@google.com>
Subject: Re: [PATCH v4] tracing: Support to dump instance traces by ftrace_dump_on_oops
Date: Wed, 7 Feb 2024 06:14:29 -0500 [thread overview]
Message-ID: <20240207061429.3e29afc8@rorschach.local.home> (raw)
In-Reply-To: <50cdbe95-c14c-49db-86aa-458e87ae9513@joelfernandes.org>
On Wed, 7 Feb 2024 05:24:58 -0500
Joel Fernandes <joel@joelfernandes.org> wrote:
> Btw, hopefully the "trace off on warning" and related boot parameters also apply
> to instances, I haven't personally checked but I often couple those with the
> dump-on-oops ones.
Currently they do not. It would require an updated interface to do so,
as sometimes instances can be used to continue tracing after a warning,
so I don't want to make it for all instances.
Perhaps we need an option for these too, and have all options be
updated via the command line. That way we don't need to make special
boot line parameters for this. If we move these to options (keeping the
proc interface for backward compatibility) it would make most features
available to all with one change.
-- Steve
next prev parent reply other threads:[~2024-02-07 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 9:46 [PATCH v4] tracing: Support to dump instance traces by ftrace_dump_on_oops Huang Yiwei
2024-02-07 10:24 ` Joel Fernandes
2024-02-07 11:14 ` Steven Rostedt [this message]
2024-02-07 14:13 ` Joel Fernandes
2024-02-08 9:22 ` Huang Yiwei
2024-02-08 9:26 ` Joel Fernandes
2024-02-08 9:36 ` Steven Rostedt
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=20240207061429.3e29afc8@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=j.granados@samsung.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kernel@quicinc.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_hyiwei@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--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