From: James Clark <James.Clark@arm.com>
To: "leo.yan@linaro.org" <leo.yan@linaro.org>,
Suzuki Poulose <Suzuki.Poulose@arm.com>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>, Mathieu Poirier <mathieu.poirier@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <Mark.Rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Igor Lubashev <ilubashe@akamai.com>
Subject: Re: [PATCH] perf tools: Fix bug when recording SPE and non SPE events
Date: Wed, 15 Jan 2020 13:15:36 +0000 [thread overview]
Message-ID: <eac2263e-07fb-ecb4-5e9f-3e215f2d4526@arm.com> (raw)
In-Reply-To: <20200113145803.GB10620@leoy-ThinkPad-X240s>
Hi Leo,
> Since SPE is defined in ARMv8 architecture reference manual (ARM DDI
> 0487D.a); should SPE trace data format is unified and defined in Chapter
> D9 "Statistical Profiling Extension Sample Record Specification"?
>
I'm not sure what you mean exactly, but the trace data format is described in
section D10.
Thanks
James
next prev parent reply other threads:[~2020-01-15 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 11:05 [PATCH] perf tools: Fix bug when recording SPE and non SPE events James Clark
2019-12-23 3:48 ` Leo Yan
2020-01-02 11:05 ` James Clark
2020-01-02 11:44 ` Leo Yan
2020-01-13 12:27 ` Suzuki Kuruppassery Poulose
2020-01-13 14:17 ` Leo Yan
2020-01-13 14:58 ` Leo Yan
2020-01-15 13:15 ` James Clark [this message]
2020-01-13 12:28 ` Suzuki Kuruppassery Poulose
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=eac2263e-07fb-ecb4-5e9f-3e215f2d4526@arm.com \
--to=james.clark@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilubashe@akamai.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nd@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).