Thread (6 messages) 6 messages, 3 authors, 2023-06-09

Re: [PATCH] tracing/timer: Add missing hrtimer modes to decode_hrtimer_mode().

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2023-05-25 00:25:37
Also in: lkml

On Wed, 24 May 2023 17:39:28 +0200
Sebastian Andrzej Siewior [off-list ref] wrote:
On 2023-04-24 17:44:41 [-0400], Steven Rostedt wrote:
quoted
On Tue, 18 Apr 2023 16:38:54 +0200
Sebastian Andrzej Siewior [off-list ref] wrote:
  
quoted
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@linutronix.de>  
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help