Linux Trace Kernel
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	 Nam Cao <namcao@linutronix.de>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Masami Hiramatsu	 <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	 Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	 Valentin Schneider	 <vschneid@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: [PATCH v3 4/5] sched: Add task enqueue/dequeue trace points
Date: Wed, 15 Jul 2026 08:51:41 +0200	[thread overview]
Message-ID: <cac78b0340121da7691ba8ffab8b7ed8350977a9.camel@redhat.com> (raw)
In-Reply-To: <20260714121145.1e73c05e@gandalf.local.home>

On Tue, 2026-07-14 at 12:11 -0400, Steven Rostedt wrote:
> On Wed, 13 Aug 2025 08:50:39 +0200
> Gabriele Monaco <gmonaco@redhat.com> wrote:
> 
> > On Mon, 2025-08-11 at 10:40 +0200, Nam Cao wrote:
> > > Add trace points into enqueue_task() and dequeue_task(). They are
> > > useful to implement RV monitor which validates RT scheduling.
> > > 
> > > Signed-off-by: Nam Cao <namcao@linutronix.de>
> > > ---  
> > 
> > Peter, Ingo, this patch adds new tracepoints in the scheduler do agree
> > with the change, can we get an Ack?
> 
> Are we still waiting on an Ack for this?

Yes, but since I'm planning to rebase the patches requiring it on other changes
I held this back. I will likely send everything for the next development cycle
after merging those new dependencies.

An Ack is surely welcome also now but not urgent.

Thanks,
Gabriele

> 
> I see it in the archive of Patchwork:
> 
>  
> https://patchwork.kernel.org/project/linux-trace-kernel/list/?series=989907&state=%2A&archive=both
> 
> -- Steve


  reply	other threads:[~2026-07-15  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11  8:40 [PATCH v3 0/5] rv: LTL per-cpu monitor type and real-time scheduling monitor Nam Cao
2025-08-11  8:40 ` [PATCH v3 1/5] rv/ltl: Prepare for other monitor types Nam Cao
2025-08-11  8:40 ` [PATCH v3 2/5] rv/ltl: Support per-cpu monitors Nam Cao
2025-08-11  8:40 ` [PATCH v3 3/5] verification/rvgen/ltl: Support per-cpu monitor generation Nam Cao
2025-08-11  8:40 ` [PATCH v3 4/5] sched: Add task enqueue/dequeue trace points Nam Cao
2025-08-13  6:50   ` Gabriele Monaco
2026-07-14 16:11     ` Steven Rostedt
2026-07-15  6:51       ` Gabriele Monaco [this message]
2026-07-15 11:31         ` Nam Cao
2026-07-15 11:38           ` Gabriele Monaco
2025-08-11  8:40 ` [PATCH v3 5/5] rv: Add rts monitor Nam Cao

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=cac78b0340121da7691ba8ffab8b7ed8350977a9.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mgorman@suse.de \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namcao@linutronix.de \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@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