linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jing Zhang <renyu.zj@linux.alibaba.com>
To: Ian Rogers <irogers@google.com>
Cc: John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-doc@vger.kernel.org,
	Zhuo Song <zhuo.song@linux.alibaba.com>,
	Shuai Xue <xueshuai@linux.alibaba.com>
Subject: Re: [PATCH v6 3/7] perf jevents: Support more event fields
Date: Mon, 14 Aug 2023 14:08:24 +0800	[thread overview]
Message-ID: <099acfd1-b32f-e325-ccd1-cfeff6667c58@linux.alibaba.com> (raw)
In-Reply-To: <50a8778a-ebe4-5b3b-9367-c8547d6d991d@oracle.com>



在 2023/8/7 下午5:24, John Garry 写道:
> On 07/08/2023 08:51, Jing Zhang wrote:
>> The usual event descriptions are "event=xxx" or "config=xxx", while the
>> event descriptions of CMN are "type=xxx, eventid=xxx" or more complex.
>>
>> $cat /sys/bus/event_source/devices/arm_cmn_0/events/hnf_cache_fill
>> type=0x5,eventid=0x3
>>
>> When adding aliases for events described as "event=xxx" or "config=xxx",
>> EventCode or ConfigCode can be used in the JSON files to describe the
>> events. But "eventid=xxx, type=xxx" cannot be supported at present.
>>
>> If EventCode and ConfigCode is not added in the alias JSON file, the
>> event description will add "event=0" by default. So, even if the event
>> field is added to supplement "eventid=xxx" and "type=xxx", the final
>> parsing result will be "event=0, eventid=xxx, type=xxx".
>>
>> Therefore, when EventCode and ConfigCode are missing in JSON, "event=0" is
>> no longer added by default. EventIdCode and Type are added to the event
>> field, and ConfigCode is moved into the event_field array which can also
>> guarantee its original function.
>>
>> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
> 
> I'll let Ian check this change as he is more familiar with this code.
> 

Hi Ian,

Could you please help to review this change?:)

Thanks,
Jing

  parent reply	other threads:[~2023-08-14  6:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  7:51 [PATCH v6 0/7] Add aliases and metrics for Arm CMN Jing Zhang
2023-08-07  7:51 ` [PATCH v6 1/7] perf pmu: "Compat" supports matching multiple identifiers Jing Zhang
2023-08-07  9:19   ` John Garry
2023-08-07  7:51 ` [PATCH v6 2/7] perf metric: " Jing Zhang
2023-08-07  9:20   ` John Garry
2023-08-07  7:51 ` [PATCH v6 3/7] perf jevents: Support more event fields Jing Zhang
2023-08-07  9:24   ` John Garry
2023-08-07 11:52     ` Jing Zhang
2023-08-14  6:08     ` Jing Zhang [this message]
2023-08-14 22:31   ` Ian Rogers
2023-08-15 12:24     ` Jing Zhang
2023-08-07  7:51 ` [PATCH v6 4/7] perf test: Fix matching_pmu Jing Zhang
2023-08-07  9:21   ` John Garry
2023-08-07 12:02     ` Jing Zhang
2023-08-07  7:51 ` [PATCH v6 5/7] perf test: Add pmu-event test for "Compat" and new event_field Jing Zhang
2023-08-07  9:23   ` John Garry
2023-08-15  1:11   ` Ian Rogers
2023-08-15 12:33     ` Jing Zhang
2023-08-07  7:51 ` [PATCH v6 6/7] perf jevents: Add support for Arm CMN PMU aliasing Jing Zhang
2023-08-14 22:36   ` Ian Rogers
2023-08-15 12:43     ` Jing Zhang
2023-08-07  7:51 ` [PATCH v6 7/7] perf vendor events: Add JSON metrics for Arm CMN Jing Zhang

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=099acfd1-b32f-e325-ccd1-cfeff6667c58@linux.alibaba.com \
    --to=renyu.zj@linux.alibaba.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --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=xueshuai@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).