[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJfuBxxKQK+X-5LW=ysPU-4mP25BnuCNxvo4xg-SgPwQsr7kXw@mail.gmail.com>
Date: Tue, 18 Jan 2022 12:18:33 -0700
From: jim.cromie@...il.com
To: Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc: "jbaron@...mai.com" <jbaron@...mai.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux@...musvillemoes.dk" <linux@...musvillemoes.dk>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"mathieu.desnoyers@...icios.com" <mathieu.desnoyers@...icios.com>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"seanpaul@...omium.org" <seanpaul@...omium.org>,
"robdclark@...il.com" <robdclark@...il.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"quic_saipraka@...cinc.com" <quic_saipraka@...cinc.com>,
"will@...nel.org" <will@...nel.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"quic_psodagud@...cinc.com" <quic_psodagud@...cinc.com>,
"maz@...nel.org" <maz@...nel.org>, "arnd@...db.de" <arnd@...db.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>
Subject: Re: [PATCH v11 03/19] dyndbg: add write-to-tracefs code
On Fri, Jan 14, 2022 at 4:46 AM Vincent Whitchurch
<vincent.whitchurch@...s.com> wrote:
>
> On Fri, Jan 07, 2022 at 06:29:26AM +0100, Jim Cromie wrote:
> >
> > Enabling debug-to-tracefs is 2 steps:
> >
> > # event enable
> > echo 1 > /sys/kernel/tracing/events/dyndbg/enable
> > # callsite enable
> > echo module foo +T > /proc/dynamic_debug/control
> >
> > This patch,~1,~2 are based upon:
> > https://lore.kernel.org/lkml/20200825153338.17061-1-vincent.whitchurch@axis.com/
> >
> > .. with simplification of temporarily reusing trace_console() rather
> > than adding a new printk:dyndbg event. Soon, add 2 new events
> > capturing the pr_debug & dev_dbg() args.
>
> The example above does not match the code in this patch since the
> dyndbg:* events are only added in a later patch. Perhaps you could
> reorder this patch stack so that you don't use trace_console() in this
> patch just to replace it with the new events in the next patch?
>
good catch, thanks.
Ive just dropped the example, it seemed the simplest fix.
It seemed proper to commit your code as pristine as practical,
so that subsequent mistakes receive the blame.
and Ive fixed the spurious whitespace change you noted.
Powered by blists - more mailing lists