From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Junhao He <hejunhao3@huawei.com>,
peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, james.clark@linaro.org,
leo.yan@arm.com, john.g.garry@oracle.com, will@kernel.org,
mike.leach@linaro.org, yangyicong@hisilicon.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] perf vendor events arm64: Fill up Desc field for Hisi hip08 hha pmu
Date: Fri, 25 Apr 2025 11:31:47 -0300 [thread overview]
Message-ID: <aAuc0xx-WqVKH0d3@x1> (raw)
In-Reply-To: <20250425120654.00007e4c@huawei.com>
On Fri, Apr 25, 2025 at 12:06:54PM +0100, Jonathan Cameron wrote:
> On Fri, 18 Apr 2025 15:08:10 +0800
> Junhao He <hejunhao3@huawei.com> wrote:
>
> > In the same PMU, when some JSON events have the "BriefDescription" field
> > populated while others do not, the cmp_sevent() function will split these
> > two types of events into separate groups. As a result, when using perf
> > list to display events, the two types of events cannot be grouped together
> > in the output.
> >
> > before patch:
> > $ perf list pmu
> > ...
> > uncore hha:
> > hisi_sccl1_hha2/sdir-hit/
> > hisi_sccl1_hha2/sdir-lookup/
> > ...
> > uncore hha:
> > edir-hit
> > [Count of The number of HHA E-Dir hit operations. Unit: hisi_sccl1_hha2]
> > ...
> >
> > after patch:
> > $ perf list pmu
> > ...
> > uncore hha:
> > edir-hit
> > [Count of The number of HHA E-Dir hit operations. Unit: hisi_sccl1_hha2]
> > sdir-hit
> > [Count of The number of HHA S-Dir hit operations. Unit: hisi_sccl1_hha2]
> > sdir-lookup
> > [Count of the number of HHA S-Dir lookup operations. Unit: hisi_sccl1_hha2]
> > ...
> >
> > Signed-off-by: Junhao He <hejunhao3@huawei.com>
> > Reviewed-by: James Clark <james.clark@linaro.org>
> One trivial comment inline that might be good to tidy up.
These can come as a follow up patch, I think.
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Applied.
- Arnaldo
next prev parent reply other threads:[~2025-04-25 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 7:08 [PATCH v2 0/3] perf vendor events arm64: Do some cleanup for Hisi hip08 json Junhao He
2025-04-18 7:08 ` [PATCH v2 1/3] perf vendor events arm64: Fill up Desc field for Hisi hip08 hha pmu Junhao He
2025-04-22 7:14 ` Yicong Yang
2025-04-25 11:06 ` Jonathan Cameron
2025-04-25 14:31 ` Arnaldo Carvalho de Melo [this message]
2025-04-18 7:08 ` [PATCH v2 2/3] perf vendor events arm64: Drop hip08 PublicDescription if same as BriefDescription Junhao He
2025-04-22 7:15 ` Yicong Yang
2025-04-25 11:08 ` Jonathan Cameron
2025-04-18 7:08 ` [PATCH v2 3/3] MAINTAINERS: Add hisilicon pmu json events under its entry Junhao He
2025-04-22 7:15 ` Yicong Yang
2025-04-25 11:09 ` Jonathan Cameron
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=aAuc0xx-WqVKH0d3@x1 \
--to=acme@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hejunhao3@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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.