From: German Gomez <german.gomez@arm.com>
To: Ali Saidi <alisaidi@amazon.com>, leo.yan@linaro.org
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
andrew.kilroy@arm.com, benh@kernel.crashing.org,
james.clark@arm.com, john.garry@huawei.com, jolsa@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mathieu.poirier@linaro.org,
mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org,
will@kernel.org
Subject: Re: [PATCH 2/2] perf arm-spe: Parse more SPE fields and store source
Date: Fri, 11 Feb 2022 16:31:40 +0000 [thread overview]
Message-ID: <7eca7a1d-a5a2-2aab-b3cf-5d83cb8ccf4f@arm.com> (raw)
In-Reply-To: <20220128210245.4628-1-alisaidi@amazon.com>
Hi Ali,
On 28/01/2022 21:02, Ali Saidi wrote:
> Hi German,
>
> On 28/01/2022 19:20, German Gomez wrote:
>> Hi Ali,
>>
>> [...]
>>> };
>>>
>>> enum arm_spe_op_type {
>>> ARM_SPE_LD = 1 << 0,
>>> ARM_SPE_ST = 1 << 1,
>>> + ARM_SPE_LDST_EXCL = 1 << 2,
>>> + ARM_SPE_LDST_ATOMIC = 1 << 3,
>>> + ARM_SPE_LDST_ACQREL = 1 << 4,
Wondering if we can store this in perf_sample->flags. The values are
defined in "util/event.h" (PERF_IP_*). Maybe we can extend it to allow
doing "sample->flags = PERF_LDST_FLAG_LD | PERF_LDST_FLAG_ATOMIC" and
such.
@Leo do you think that could work?
>>> + ARM_SPE_BR = 1 << 5,
>>> + ARM_SPE_BR_COND = 1 << 6,
>>> + ARM_SPE_BR_IND = 1 << 7,
Seems like we can store BR_COND in the existing "branch-miss" event
(--itrace=b) with:
sample->flags = PERF_IP_FLAG_BRANCH;
sample->flags |= PERF_IP_FLAG_CONDITIONAL;
and/or
sample->flags |= PERF_IP_FLAG_INDIRECT;
PERF_IP_FLAG_INDIRECT doesn't exist yet but we can probably add it.
next prev parent reply other threads:[~2022-02-11 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 19:20 [PATCH 0/2] Allow perf scripts to process SPE raw data Ali Saidi
2022-01-25 19:20 ` [PATCH 1/2] perf arm-spe: Add arm_spe_record to synthesized sample Ali Saidi
2022-01-25 20:47 ` German Gomez
2022-01-26 15:58 ` [PATCH 1/2] perf arm-spe: Add arm_spe_record to synthesized Ali Saidi
2022-01-26 19:07 ` German Gomez
2022-01-27 19:13 ` Ali Saidi
2022-01-25 19:20 ` [PATCH 2/2] perf arm-spe: Parse more SPE fields and store source Ali Saidi
2022-01-28 17:20 ` German Gomez
2022-01-28 21:02 ` Ali Saidi
2022-02-11 16:31 ` German Gomez [this message]
2022-02-12 4:19 ` Leo Yan
2022-02-21 20:41 ` German Gomez
2022-02-22 19:29 ` Ali Saidi
2022-02-25 12:40 ` German Gomez
2022-02-27 13:54 ` Leo Yan
2022-02-27 13:20 ` Leo Yan
2022-03-01 10:54 ` German Gomez
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=7eca7a1d-a5a2-2aab-b3cf-5d83cb8ccf4f@arm.com \
--to=german.gomez@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.com \
--cc=andrew.kilroy@arm.com \
--cc=benh@kernel.crashing.org \
--cc=james.clark@arm.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
all inboxes | Powered by JetHome®