[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230524202526.289e3a65@rorschach.local.home>
Date: Wed, 24 May 2023 20:25:26 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] tracing/timer: Add missing hrtimer modes to
decode_hrtimer_mode().
On Wed, 24 May 2023 17:39:28 +0200
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> On 2023-04-24 17:44:41 [-0400], Steven Rostedt wrote:
> > On Tue, 18 Apr 2023 16:38:54 +0200
> > Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> >
> > > The trace output for the HRTIMER_MODE_.*_HARD modes is seen as a number
> > > since these modes are not decoded. The author was not aware of the fancy
> > > decoding function which makes the life easier.
> > >
> > > Extend decode_hrtimer_mode() with the additional HRTIMER_MODE_.*_HARD
> > > modes.
> > >
> > > Fixes: ae6683d815895 ("hrtimer: Introduce HARD expiry mode")
> > > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> >
> > Acked-by: Steven Rostedt (Google) <rostedt@...dmis.org>
>
> Could this be either routed via the tracing tree or the tip tree but
> please route this :)
>
Events are normally owned by the subsystem they are used in. So it
should go through tip. But if I get an ack from the subsystem
maintainer, I can route it through tracing.
-- Steve
Powered by blists - more mailing lists