[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221008164451.738c912c@rorschach.local.home>
Date: Sat, 8 Oct 2022 16:44:51 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
Ingo Molnar <mingo@...hat.com>, linux-watchdog@...r.kernel.org,
kernel@...gutronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] watchdog: Add tracing events for the most usual
watchdog events
On Sat, 8 Oct 2022 19:46:02 +0200
Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote:
> To simplify debugging which process touches a watchdog and when, add
> tracing events for .start(), .set_timeout(), .ping() and .stop().
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
> ---
> Changes since v2 sent with Message-Id:
> 20221004091950.3419662-1-u.kleine-koenig@...gutronix.de:
>
> - Reorder events in the header to have all DEFINE_EVENTS near their
> DECLARE_EVENT_CLASS.
>
Reviewed-by: Steven Rostedt (Google) <rostedt@...dmis.org>
-- Steve
Powered by blists - more mailing lists