[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240229102537.28d46135@gandalf.local.home>
Date: Thu, 29 Feb 2024 10:25:37 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Huang Yiwei <quic_hyiwei@...cinc.com>
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>, Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH v5] tracing: Support to dump instance traces by
ftrace_dump_on_oops
On Thu, 29 Feb 2024 17:11:49 +0800
Huang Yiwei <quic_hyiwei@...cinc.com> wrote:
> > And you can add here as well:
> >
> > ftrace_dump_on_oops[=[<0|1|2|orig_cpu>,][<instance_name>[=<1|2|orig_cpu>][,...]]
> >
> >
> > Thanks,
> >
> > --Steve
> >
> The explanation is below, I think it's correct?
> - "ftrace_dump_on_oops," means global buffer on all CPUs
> - "foo," means foo instance on all CPUs
> - "bar=orig_cpu" means bar instance on CPU that triggered the oops.
>
> I'm trying to make the example to cover more possibilities.
Ah, I didn't think the command line processing would work with commas. I
guess it does (I just tried it out).
OK, then I guess that's fine.
-- Steve
Powered by blists - more mailing lists