From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>, Xu Yang <xu.yang_2@nxp.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Collin Funk <collin.funk1@gmail.com>,
Howard Chu <howardchu95@gmail.com>,
Weilin Wang <weilin.wang@intel.com>,
Andi Kleen <ak@linux.intel.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Thomas Richter <tmricht@linux.ibm.com>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Gautam Menghani <gautam@linux.ibm.com>,
Thomas Falcon <thomas.falcon@intel.com>,
Chun-Tse Shao <ctshao@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v9 00/16] New perf ilist app
Date: Sat, 26 Jul 2025 16:22:26 -0700 [thread overview]
Message-ID: <aIVjMrRLkL5Z5Xnm@google.com> (raw)
In-Reply-To: <aIVg3X5ByiTPkXRA@google.com>
On Sat, Jul 26, 2025 at 04:12:29PM -0700, Namhyung Kim wrote:
> Hi Ian,
>
> On Fri, Jul 25, 2025 at 11:51:46AM -0700, Ian Rogers wrote:
> > This patch series builds up to the addition of a new ilist app written
> > in python using textual [1] for the UI. The app presents perf PMUs and
> > events, displays the event information as in `perf list` while at the
> > bottom of the console showing recent activity of the event in total
> > and across all CPUs. It also displays metrics, placed in a tree
> > through their metric group, again with counts being displayed in the
> > bottom panel.
> >
> > The first ground work patches of fixes, cleanup and refactoring were
> > separated into their own series here:
> > https://lore.kernel.org/lkml/20250709214029.1769089-1-irogers@google.com/
> >
> > The second part of the patches adds event json for the software PMU
> > and makes the tracepoint PMU support iteration of events and the
> > like. Without these improvements the tracepoint and software PMUs will
> > appear to have no events in the ilist app. As the software PMU moves
> > parsing to json, the legacy hard coded parsing is removed. This has
> > proven controversial for hardware events and so that cleanup isn't
> > done here.
>
> Even software PMU can be controversial. :) But I think we can try this
> first. Basically this will change the output `perf list` and the event
> parsing behavior.
>
> For example, `perf list sw` will look like:
>
> software:
> alignment-faults
> [Number of kernel handled memory alignment faults. Unit: software]
> bpf-output
> [An event used by BPF programs to write to the perf ring buffer. Unit: software]
> cgroup-switches
> [Number of context switches to a task in a different cgroup. Unit: software]
> context-switches
> [Number of context switches [This event is an alias of cs]. Unit: software]
> cpu-clock
> [Per-CPU high-resolution timer based event. Unit: software]
> cpu-migrations
> [Number of times a process has migrated to a new CPU [This event is an alias of migrations]. Unit: software]
> cs
> [Number of context switches [This event is an alias of context-switches]. Unit: software]
> dummy
> [A placeholder event that doesn't count anything. Unit: software]
> ...
>
> Let's add this change and see if people complain..
>
> Btw, I think the alias can be one-way. IOW 'context-switches' is a
> software event and 'cs' is an alias to it, not vice versa. I'll make
> the change.
Hmm.. this needs to rebuild the string index and causes a build error.
I'll just leave it as is and we can update it later.
Thanks,
Namhyung
next prev parent reply other threads:[~2025-07-26 23:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 18:51 [PATCH v9 00/16] New perf ilist app Ian Rogers
2025-07-25 18:51 ` [PATCH v9 01/16] perf python: Add more exceptions on error paths Ian Rogers
2025-07-25 18:51 ` [PATCH v9 02/16] perf jevents: Add common software event json Ian Rogers
2025-07-25 18:51 ` [PATCH v9 03/16] perf parse-events: Remove non-json software events Ian Rogers
2025-07-25 18:51 ` [PATCH v9 04/16] perf tp_pmu: Factor existing tracepoint logic to new file Ian Rogers
2025-08-05 22:57 ` Howard Chu
2025-07-25 18:51 ` [PATCH v9 05/16] perf tp_pmu: Add event APIs Ian Rogers
2025-07-25 18:51 ` [PATCH v9 06/16] perf list: Remove tracepoint printing code Ian Rogers
2025-07-25 18:51 ` [PATCH v9 07/16] perf list: Skip ABI PMUs when printing pmu values Ian Rogers
2025-07-25 18:51 ` [PATCH v9 08/16] perf python: Improve the tracepoint function if no libtraceevent Ian Rogers
2025-07-25 18:51 ` [PATCH v9 09/16] perf python: Add basic PMU abstraction and pmus sequence Ian Rogers
2025-07-25 18:51 ` [PATCH v9 10/16] perf python: Add function returning dictionary of all events on a PMU Ian Rogers
2025-08-05 22:58 ` Howard Chu
2025-07-25 18:51 ` [PATCH v9 11/16] perf ilist: Add new python ilist command Ian Rogers
2025-08-05 23:05 ` Howard Chu
2025-08-18 22:13 ` Ian Rogers
2025-07-25 18:51 ` [PATCH v9 12/16] perf python: Add parse_metrics function Ian Rogers
2025-07-25 18:51 ` [PATCH v9 13/16] perf python: Add evlist metrics function Ian Rogers
2025-07-25 18:52 ` [PATCH v9 14/16] perf python: Add evlist compute_metric Ian Rogers
2025-07-25 18:52 ` [PATCH v9 15/16] perf python: Add metrics function Ian Rogers
2025-07-25 18:52 ` [PATCH v9 16/16] perf ilist: Add support for metrics Ian Rogers
2025-07-26 23:12 ` [PATCH v9 00/16] New perf ilist app Namhyung Kim
2025-07-26 23:22 ` Namhyung Kim [this message]
2025-07-28 18:04 ` Namhyung Kim
2025-08-05 23:25 ` Howard Chu
2025-08-06 3:15 ` Howard Chu
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=aIVjMrRLkL5Z5Xnm@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=collin.funk1@gmail.com \
--cc=ctshao@google.com \
--cc=gautam@linux.ibm.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=tmricht@linux.ibm.com \
--cc=weilin.wang@intel.com \
--cc=xu.yang_2@nxp.com \
--cc=yangtiezhu@loongson.cn \
/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.