From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ian Rogers <irogers@google.com>,
"Chen, Yu C" <yu.c.chen@intel.com>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
ravi.bangoria@amd.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
rostedt@goodmis.org, vincent.guittot@linaro.org,
adrian.hunter@intel.com, kan.liang@linux.intel.com,
gautham.shenoy@amd.com, kprateek.nayak@amd.com,
juri.lelli@redhat.com, yangjihong@bytedance.com,
void@manifault.com, tj@kernel.org, sshegde@linux.ibm.com,
ctshao@google.com, quic_zhonhan@quicinc.com,
thomas.falcon@intel.com, blakejones@google.com,
ashelat@redhat.com, leo.yan@arm.com, dvyukov@google.com,
ak@linux.intel.com, yujie.liu@intel.com, graham.woodward@arm.com,
ben.gainey@arm.com, vineethr@linux.ibm.com,
tim.c.chen@linux.intel.com, linux@treblig.org,
santosh.shukla@amd.com, sandipan.das@amd.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mingo@redhat.com, namhyung@kernel.org, james.clark@arm.com
Subject: Re: [PATCH v5 00/10] perf sched: Introduce stats tool
Date: Wed, 21 Jan 2026 17:08:04 -0300 [thread overview]
Message-ID: <aXEyJCSqlPPUS9YG@x1> (raw)
In-Reply-To: <20260121195155.GP166857@noisy.programming.kicks-ass.net>
On Wed, Jan 21, 2026 at 08:51:55PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 21, 2026 at 09:12:20AM -0800, Ian Rogers wrote:
>
> > I'm still wondering if we can make some of the /proc/schedstat data
> > appear as tool events similar to proposals for networking and memory
> > tool events in:
> > https://lore.kernel.org/lkml/20260104011738.475680-1-irogers@google.com/
>
> Yeah, someone with a bit of spare time could make it happen:
>
> https://lkml.kernel.org/r/20250703141800.GX1613200@noisy.programming.kicks-ass.net
>
> It would be:
>
> - convert all the accounting sites to tracepoints
> - write modules that connect to relevant tracepoints to provide the
> 'legacy' interface
> - convince world+dog to not auto-load above modules
> - have beer and wait for people to complain about something :-)
>
> I'm sure there's 'interesting' details glossed over, but I *think* it
> should be doable.
Until then, since you and Ian acked this one, I'm going over it and
tentatively merging it,
Thanks,
- Arnaldo
next prev parent reply other threads:[~2026-01-21 20:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 17:58 [PATCH v5 00/10] perf sched: Introduce stats tool Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 01/10] tools/lib: Add list_is_first() Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 02/10] perf header: Support CPU DOMAIN relation info Swapnil Sapkal
2026-01-21 17:18 ` Shrikanth Hegde
2026-01-23 15:19 ` Swapnil Sapkal
2026-01-23 16:31 ` Arnaldo Carvalho de Melo
2026-01-26 14:46 ` kernel test robot
2026-01-26 17:12 ` Ian Rogers
2026-01-27 2:46 ` Oliver Sang
2026-01-19 17:58 ` [PATCH v5 03/10] perf sched stats: Add record and rawdump support Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 04/10] perf sched stats: Add schedstat v16 support Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 05/10] perf sched stats: Add schedstat v17 support Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 06/10] perf sched stats: Add support for report subcommand Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 07/10] perf sched stats: Add support for live mode Swapnil Sapkal
2026-01-22 0:54 ` Arnaldo Carvalho de Melo
2026-01-22 1:32 ` Arnaldo Carvalho de Melo
2026-01-22 15:34 ` Arnaldo Carvalho de Melo
2026-01-22 15:42 ` Arnaldo Carvalho de Melo
2026-03-03 18:47 ` Ian Rogers
2026-03-10 10:08 ` Swapnil Sapkal
2026-03-30 14:35 ` James Clark
2026-04-01 7:04 ` Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 08/10] perf sched stats: Add support for diff subcommand Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 09/10] perf sched stats: Add basic perf sched stats test Swapnil Sapkal
2026-01-19 17:58 ` [PATCH v5 10/10] perf sched stats: Add details in man page Swapnil Sapkal
2026-01-21 16:09 ` [PATCH v5 00/10] perf sched: Introduce stats tool Chen, Yu C
2026-01-21 16:33 ` Peter Zijlstra
2026-01-21 17:12 ` Ian Rogers
2026-01-21 19:51 ` Peter Zijlstra
2026-01-21 20:08 ` Arnaldo Carvalho de Melo [this message]
2026-01-21 20:10 ` Peter Zijlstra
2026-01-22 16:00 ` Arnaldo Carvalho de Melo
2026-01-23 16:32 ` Swapnil Sapkal
2026-01-23 16:37 ` Arnaldo Carvalho de Melo
2026-01-23 16:42 ` Swapnil Sapkal
2026-01-21 17:52 ` Shrikanth Hegde
2026-01-23 16:19 ` Swapnil Sapkal
2026-01-21 22:59 ` Namhyung Kim
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=aXEyJCSqlPPUS9YG@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ashelat@redhat.com \
--cc=ben.gainey@arm.com \
--cc=blakejones@google.com \
--cc=ctshao@google.com \
--cc=dvyukov@google.com \
--cc=gautham.shenoy@amd.com \
--cc=graham.woodward@arm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_zhonhan@quicinc.com \
--cc=ravi.bangoria@amd.com \
--cc=rostedt@goodmis.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=sshegde@linux.ibm.com \
--cc=swapnil.sapkal@amd.com \
--cc=thomas.falcon@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=void@manifault.com \
--cc=yangjihong@bytedance.com \
--cc=yu.c.chen@intel.com \
--cc=yujie.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.