[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02e7de82c4093adcbd82aaabaab893f43abcea9c.camel@redhat.com>
Date: Fri, 16 Jan 2026 15:24:43 +0100
From: Gabriele Monaco <gmonaco@...hat.com>
To: Phil Auld <pauld@...hat.com>
Cc: linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>, Nam
Cao <namcao@...utronix.de>, Juri Lelli <jlelli@...hat.com>, Ingo Molnar
<mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>, Tomas Glozar
<tglozar@...hat.com>, Clark Williams <williams@...hat.com>, John Kacur
<jkacur@...hat.com>, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v4 08/15] sched: Export hidden tracepoints to modules
On Fri, 2026-01-16 at 09:00 -0500, Phil Auld wrote:
> Hi Gabriele,
>
> On Fri, Jan 16, 2026 at 01:39:04PM +0100 Gabriele Monaco wrote:
> > The tracepoints sched_entry, sched_exit and sched_set_need_resched
> > are not exported to tracefs as trace events, this allows only kernel
> > code to access them. Helper modules like [1] can be used to still have
> > the tracepoints available to ftrace for debugging purposes, but they do
> > rely on the tracepoints being exported.
> >
> > Export the 3 not exported tracepoints.
> > Note that sched_set_state is already exported as the macro is called
> > from modules.
> >
> > [1] - https://github.com/qais-yousef/sched_tp.git
> >
> > Fixes: adcc3bfa8806 ("sched: Adapt sched tracepoints for RV task model")
> > Reviewed-by: Phil Auld <pauld@...hat.com>
> > Signed-off-by: Gabriele Monaco <gmonaco@...hat.com>
>
> You can probably skip this one now, yes?
Right, I kept it here only to avoid conflicts and didn't mention it in the cover
letter.. But yes, since this is part of tip, it can be skipped from the series.
Gabriele
Powered by blists - more mailing lists