From: James Clark <james.clark@arm.com>
To: Leo Yan <leo.yan@linaro.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Grant <Al.Grant@arm.com>
Subject: Re: [PATCH v1 2/3] perf arm-spe: Correct sample flags for dummy event
Date: Wed, 12 May 2021 18:17:03 +0300 [thread overview]
Message-ID: <95d93dcb-e930-a1c7-08e1-be8885d19f64@arm.com> (raw)
In-Reply-To: <f4e483ae-acbb-7afa-c215-cb4244c2e820@arm.com>
On 12/05/2021 17:39, James Clark wrote:
>
>
> On 29/04/2021 18:00, Leo Yan wrote:
>> The dummy event is mainly used for mmap, the TIME sample is only needed
[...]
>> - tracking_evsel->core.attr.freq = 0;
>> - tracking_evsel->core.attr.sample_period = 1;
>> - evsel__set_sample_bit(tracking_evsel, TIME);
>> - evsel__set_sample_bit(tracking_evsel, CPU);
>> - evsel__reset_sample_bit(tracking_evsel, BRANCH_STACK);
>> + if (opts->full_auxtrace) {
>> + struct evsel *tracking_evsel;
>
> Hi Leo,
>
> I know the "if (opts->full_auxtrace)" pattern is copied from other auxtrace
> files, but I don't think it does anything because there is this at the top
> of the function:
>
> if (!opts->full_auxtrace)
> return 0;
>
> The same applies for other usages of "full_auxtrace" in the same function.
> They are all always true. I'm also not sure if it's ever defined what
> full_auxtrace means.
>
> James
Apart from this issue above, I've tested the full patchset with various combinations
of --per-thread, -a and --timestamp and don't see any issues like missing command names
or decode issues. (Apart from -a where Command is reported as '-1', but this issue is
present before and after this patchset so is unrelated.)
I think it makes sense to unify the behaviour to make it more like Coresight and others
so this is a good change.
Reviewed-by: James Clark <james.clark@arm.com>
Tested-by: James Clark <james.clark@arm.com>
>
>> +
>> + err = parse_events(evlist, "dummy:u", NULL);
>> + if (err)
>> + return err;
>> +
>> + tracking_evsel = evlist__last(evlist);
>> + evlist__set_tracking_event(evlist, tracking_evsel);
>> +
>> + tracking_evsel->core.attr.freq = 0;
>> + tracking_evsel->core.attr.sample_period = 1;
>> +
>> + /* In per-cpu case, always need the time of mmap events etc */
>> + if (!perf_cpu_map__empty(cpus))
>> + evsel__set_sample_bit(tracking_evsel, TIME);
>> + }
>>
>> return 0;
>> }
>>
next prev parent reply other threads:[~2021-05-12 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 15:00 [PATCH v1 0/3] perf arm-spe: Correct recording configurations Leo Yan
2021-04-29 15:00 ` [PATCH v1 1/3] perf arm-spe: Correct sample flags for SPE event Leo Yan
2021-04-29 15:00 ` [PATCH v1 2/3] perf arm-spe: Correct sample flags for dummy event Leo Yan
2021-05-12 14:39 ` James Clark
2021-05-12 15:17 ` James Clark [this message]
2021-05-12 15:37 ` Leo Yan
2021-05-12 15:23 ` Leo Yan
2021-05-18 12:54 ` Arnaldo Carvalho de Melo
2021-05-18 14:18 ` Leo Yan
2021-04-29 15:01 ` [PATCH v1 3/3] perf arm-spe: Enable timestamp for per-cpu mode Leo Yan
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=95d93dcb-e930-a1c7-08e1-be8885d19f64@arm.com \
--to=james.clark@arm.com \
--cc=Al.Grant@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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).