From: James Clark <james.clark@arm.com>
To: German Gomez <german.gomez@arm.com>, Leo Yan <leo.yan@linaro.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
Stephane Eranian <eranian@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [RFC] perf arm-spe: Track task context switch for cpu-mode events
Date: Wed, 6 Oct 2021 15:06:25 +0100 [thread overview]
Message-ID: <4ec2508a-d87a-ad91-87ec-dadef71bbc78@arm.com> (raw)
In-Reply-To: <f877cfa6-9b25-6445-3806-ca44a4042eaf@arm.com>
On 05/10/2021 11:06, German Gomez wrote:
> Hi Leo,
>
> On 04/10/2021 07:26, Leo Yan wrote:
>> Hi James,
>>
>> On Thu, Sep 30, 2021 at 04:08:52PM +0100, James Clark wrote:
>>> On 23/09/2021 15:23, Leo Yan wrote:
>>>> On Thu, Sep 16, 2021 at 02:01:21PM -0700, Namhyung Kim wrote:
>> [...]
>> I'd like to use the comparison method for the test:
>> We should enable PID tracing and capture in the perf.data, when decode
>> the trace data, we can based on context packet and based on the switch
>> events to generate out two results, so we can check how the difference
>> between these results.
>
> Yesterday we did some testing and found that there seems to be an exact
> match between using context packets and switch events. However this only
> applies when tracing in userspace (by adding the 'u' suffix to the perf
> event). Otherwise we still see as much as 2% of events having the wrong
> PID around the time of the switch.
>
> In order to measure this I applied Namhyung's patch and James's patch
> from [1].
I thought that this had been applied already so I need to follow this up.
James
[...]
>
> [1] https://www.spinics.net/lists/linux-perf-users/msg12543.html
>
prev parent reply other threads:[~2021-10-06 14:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 0:17 Namhyung Kim
2021-09-16 13:54 ` Leo Yan
2021-09-16 21:01 ` Namhyung Kim
2021-09-23 14:23 ` Leo Yan
2021-09-23 16:01 ` Namhyung Kim
2021-09-30 18:47 ` Stephane Eranian
2021-10-01 10:44 ` James Clark
2021-10-01 18:22 ` Stephane Eranian
2021-10-04 15:19 ` Leo Yan
2021-09-30 15:08 ` James Clark
2021-10-04 6:26 ` Leo Yan
2021-10-05 10:06 ` German Gomez
2021-10-06 9:36 ` Leo Yan
2021-10-06 16:09 ` Namhyung Kim
2021-10-08 11:07 ` German Gomez
2021-10-09 0:12 ` Namhyung Kim
2021-10-11 13:58 ` German Gomez
2021-10-11 14:29 ` Leo Yan
2021-10-12 11:07 ` German Gomez
2021-10-18 11:01 ` German Gomez
2021-10-18 13:23 ` Leo Yan
2021-10-19 12:21 ` German Gomez
2021-10-29 10:51 ` German Gomez
2021-11-01 15:11 ` Leo Yan
2021-11-01 15:36 ` German Gomez
2021-11-01 15:42 ` German Gomez
2021-10-06 14:06 ` James Clark [this message]
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=4ec2508a-d87a-ad91-87ec-dadef71bbc78@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=german.gomez@arm.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome