[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <497fdb48-9fce-444e-8d51-2073a37f697d@joelfernandes.org>
Date: Thu, 8 Feb 2024 04:26:30 -0500
From: Joel Fernandes <joel@...lfernandes.org>
To: Huang Yiwei <quic_hyiwei@...cinc.com>,
Steven Rostedt <rostedt@...dmis.org>
Cc: mhiramat@...nel.org, mark.rutland@....com, mcgrof@...nel.org,
keescook@...omium.org, j.granados@...sung.com,
mathieu.desnoyers@...icios.com, corbet@....net,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
quic_bjorande@...cinc.com, quic_tsoni@...cinc.com, quic_satyap@...cinc.com,
quic_aiquny@...cinc.com, kernel@...cinc.com,
Ross Zwisler <zwisler@...gle.com>
Subject: Re: [PATCH v4] tracing: Support to dump instance traces by
ftrace_dump_on_oops
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
Powered by blists - more mailing lists