From: Leo Yan <leo.yan@linaro.org>
To: John Garry <john.garry@huawei.com>
Cc: Yicong Yang <yangyicong@huawei.com>,
acme@kernel.org, peterz@infradead.org,
alexander.shishkin@linux.intel.com, james.clark@arm.com,
will@kernel.org, mathieu.poirier@linaro.org,
mark.rutland@arm.com, suzuki.poulose@arm.com,
jonathan.cameron@huawei.com, mike.leach@linaro.org,
gregkh@linuxfoundation.org, helgaas@kernel.org,
lorenzo.pieralisi@arm.com, shameerali.kolothum.thodi@huawei.com,
mingo@redhat.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
linux-perf-users@vger.kernel.org, prime.zeng@huawei.com,
zhangshaokun@hisilicon.com, linuxarm@huawei.com,
yangyicong@hisilicon.com, liuqi6124@gmail.com
Subject: Re: [RESEND PATCH v12 1/3] perf tool: arm: Refactor event list iteration in auxtrace_record__init()
Date: Wed, 14 Sep 2022 22:27:23 +0800 [thread overview]
Message-ID: <YyHkywZUVPL3GNq8@leoy-yangtze.lan> (raw)
In-Reply-To: <c5577971-946e-405b-b0ee-23b556ea3f72@huawei.com>
On Wed, Sep 14, 2022 at 02:47:43PM +0100, John Garry wrote:
[...]
> > struct auxtrace_record
> > *auxtrace_record__init(struct evlist *evlist, int *err)
> > {
> > - struct perf_pmu *cs_etm_pmu;
> > + struct perf_pmu *cs_etm_pmu = NULL;
> > + struct perf_pmu **arm_spe_pmus = NULL;
> > struct evsel *evsel;
> > - bool found_etm = false;
> > + struct perf_pmu *found_etm = NULL;
> > struct perf_pmu *found_spe = NULL;
> > - struct perf_pmu **arm_spe_pmus = NULL;
> > + int auxtrace_event_cnt = 0;
> > int nr_spes = 0;
> > - int i = 0;
> > if (!evlist)
> > return NULL;
> > @@ -68,24 +84,23 @@ struct auxtrace_record
> > arm_spe_pmus = find_all_arm_spe_pmus(&nr_spes, err);
> > evlist__for_each_entry(evlist, evsel) {
> > - if (cs_etm_pmu &&
> > - evsel->core.attr.type == cs_etm_pmu->type)
> > - found_etm = true;
> > -
> > - if (!nr_spes || found_spe)
> > - continue;
> > -
> > - for (i = 0; i < nr_spes; i++) {
> > - if (evsel->core.attr.type == arm_spe_pmus[i]->type) {
> > - found_spe = arm_spe_pmus[i];
> > - break;
> > - }
> > - }
> > + if (cs_etm_pmu && !found_etm) + found_etm =
> > find_pmu_for_event(&cs_etm_pmu, 1, evsel);
> > +
> > + if (arm_spe_pmus && !found_spe)
> > + found_spe = find_pmu_for_event(arm_spe_pmus, nr_spes, evsel);
>
> should you break if found_etm and found_spe are set? Or, indeed, error and
> return directly as we do below? Indeed, I am not sure why you even require
> auxtrace_event_cnt
I think this was my suggestion :)
We can check if both 'found_etm' and 'found_spe' are set and directly
break (and bail out) for this case. But it would introduce more complex
checking if we connect with patch 2 with new flag 'found_ptt', something
like:
if ((found_etm && found_spe) ||
(found_etm && found_ptt) ||
(found_spe && found_ptt))
break;
This is hard for later's extension if we need to support a new auxtrace
event, so using auxtrace_event_cnt would be easier to extend more
auxtrace event on Arm platforms.
Thanks,
Leo
> > }
> > +
> > free(arm_spe_pmus);
> > - if (found_etm && found_spe) {
> > - pr_err("Concurrent ARM Coresight ETM and SPE operation not currently supported\n");
> > + if (found_etm)
> > + auxtrace_event_cnt++;
> > +
> > + if (found_spe)
> > + auxtrace_event_cnt++;
> > +
> > + if (auxtrace_event_cnt > 1) {
> > + pr_err("Concurrent AUX trace operation not currently supported\n");
> > *err = -EOPNOTSUPP;
> > return NULL;
> > }
>
next prev parent reply other threads:[~2022-09-14 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 7:59 [RESEND PATCH v12 0/3] Add perf support for HiSilicon PCIe Tune and Trace device Yicong Yang
2022-09-14 7:59 ` [RESEND PATCH v12 1/3] perf tool: arm: Refactor event list iteration in auxtrace_record__init() Yicong Yang
2022-09-14 13:47 ` John Garry
2022-09-14 14:27 ` Leo Yan [this message]
2022-09-15 3:57 ` Yicong Yang
2022-09-14 7:59 ` [RESEND PATCH v12 2/3] perf tool: Add support for HiSilicon PCIe Tune and Trace device driver Yicong Yang
2022-09-14 7:59 ` [RESEND PATCH v12 3/3] perf tool: Add support for parsing HiSilicon PCIe Trace packet Yicong Yang
2022-09-14 10:12 ` John Garry
2022-09-15 4:06 ` Yicong Yang
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=YyHkywZUVPL3GNq8@leoy-yangtze.lan \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuqi6124@gmail.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=prime.zeng@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.com \
--cc=zhangshaokun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox