From: Joel Fernandes <joel@joelfernandes.org>
To: Huang Yiwei <quic_hyiwei@quicinc.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: 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: Thu, 8 Feb 2024 04:26:30 -0500 [thread overview]
Message-ID: <497fdb48-9fce-444e-8d51-2073a37f697d@joelfernandes.org> (raw)
In-Reply-To: <ec99fdee-8d3f-476f-842f-f57b2b817dae@quicinc.com>
On 2/8/2024 4:22 AM, Huang Yiwei wrote:
>
>
> On 2/7/2024 10:13 PM, Joel Fernandes wrote:
[..]
>>> 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.
> It's a good idea that "traceoff_on_warning" also has instance support, but we
> will use another patchset to do this, right?
>
> And for this patchset, shall I fix the typo and resend again? Thanks.
That is fine with me but it is up to tracing maintainers. ;-)
- Joel
next prev parent reply other threads:[~2024-02-08 9:26 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
2024-02-07 14:13 ` Joel Fernandes
2024-02-08 9:22 ` Huang Yiwei
2024-02-08 9:26 ` Joel Fernandes [this message]
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=497fdb48-9fce-444e-8d51-2073a37f697d@joelfernandes.org \
--to=joel@joelfernandes.org \
--cc=corbet@lwn.net \
--cc=j.granados@samsung.com \
--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=rostedt@goodmis.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