From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Gabriele Monaco <gmonaco@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH v5 1/9] sched: Add sched tracepoints for RV task model
Date: Mon, 24 Mar 2025 12:35:55 +0100 [thread overview]
Message-ID: <20250324113555.GC14944@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250307123849.1e5d7543@gandalf.local.home>
On Fri, Mar 07, 2025 at 12:38:49PM -0500, Steven Rostedt wrote:
>
> Can I get an Acked-by from one of the scheduler maintainers?
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2025-03-24 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 14:03 [PATCH v5 0/9] rv: Add scheduler specification monitors Gabriele Monaco
2025-03-05 14:03 ` [PATCH v5 1/9] sched: Add sched tracepoints for RV task model Gabriele Monaco
2025-03-07 17:38 ` Steven Rostedt
2025-03-24 11:35 ` Peter Zijlstra [this message]
2025-03-05 14:03 ` [PATCH v5 2/9] rv: Add option for nested monitors and include sched Gabriele Monaco
2025-03-05 14:03 ` [PATCH v5 3/9] rv: Add sco and tss per-cpu monitors Gabriele Monaco
2025-03-05 14:03 ` [PATCH v5 4/9] rv: Add snroc per-task monitor Gabriele Monaco
2025-03-05 14:03 ` [PATCH v5 5/9] rv: Add scpd, snep and sncid per-cpu monitors Gabriele Monaco
2025-03-05 14:03 ` [PATCH v5 6/9] tools/rv: Add support for nested monitors Gabriele Monaco
2025-03-05 14:04 ` [PATCH v5 7/9] verification/dot2k: " Gabriele Monaco
2025-03-05 14:04 ` [PATCH v5 8/9] Documentation/rv: Add docs for the sched monitors Gabriele Monaco
2025-03-05 14:04 ` [PATCH v5 9/9] tools/rv: Allow rv list to filter for container 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=20250324113555.GC14944@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).