From: Gabriele Monaco <gmonaco@redhat.com>
To: Phil Auld <pauld@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Nam Cao <namcao@linutronix.de>, Juri Lelli <jlelli@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Tomas Glozar <tglozar@redhat.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v4 08/15] sched: Export hidden tracepoints to modules
Date: Fri, 16 Jan 2026 15:24:43 +0100 [thread overview]
Message-ID: <02e7de82c4093adcbd82aaabaab893f43abcea9c.camel@redhat.com> (raw)
In-Reply-To: <20260116140047.GA1129681@pauld.westford.csb>
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@redhat.com>
> > Signed-off-by: Gabriele Monaco <gmonaco@redhat.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
next prev parent reply other threads:[~2026-01-16 14:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 12:38 [PATCH v4 00/15] rv: Add Hybrid Automata monitor type, per-object and deadline monitors Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 01/15] rv: Unify DA event handling functions across monitor types Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 02/15] rv: Add Hybrid Automata monitor type Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 03/15] verification/rvgen: Allow spaces in and events strings Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 04/15] verification/rvgen: Add support for Hybrid Automata Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 05/15] Documentation/rv: Add documentation about hybrid automata Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 06/15] rv: Add sample hybrid monitors stall Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 07/15] rv: Convert the opid monitor to a hybrid automaton Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 08/15] sched: Export hidden tracepoints to modules Gabriele Monaco
2026-01-16 14:00 ` Phil Auld
2026-01-16 14:24 ` Gabriele Monaco [this message]
2026-01-16 12:39 ` [PATCH v4 09/15] sched: Add deadline tracepoints Gabriele Monaco
2026-01-19 10:20 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 10/15] sched: Add task enqueue/dequeue trace points Gabriele Monaco
2026-01-16 14:50 ` K Prateek Nayak
2026-01-16 15:01 ` Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 11/15] rv: Add support for per-object monitors in DA/HA Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 12/15] verification/rvgen: Add support for per-obj monitors Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 13/15] sched/deadline: Move some utility functions to deadline.h Gabriele Monaco
2026-01-19 10:08 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 14/15] rv: Add deadline monitors Gabriele Monaco
2026-01-19 11:04 ` Juri Lelli
2026-01-19 11:35 ` Gabriele Monaco
2026-01-19 13:16 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 15/15] rv: Add dl_server specific monitors Gabriele Monaco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02e7de82c4093adcbd82aaabaab893f43abcea9c.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=jkacur@redhat.com \
--cc=jlelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namcao@linutronix.de \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox