From: James Clark <james.clark@arm.com>
To: coresight@lists.linaro.org, mathieu.poirier@linaro.org, acme@kernel.org
Cc: al.grant@arm.com, branislav.rankov@arm.com, denik@chromium.org,
suzuki.poulose@arm.com, anshuman.khandual@arm.com,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] perf cs-etm: Set time on synthesised samples to preserve ordering
Date: Mon, 10 May 2021 17:32:46 +0300 [thread overview]
Message-ID: <20210510143248.27423-1-james.clark@arm.com> (raw)
Changes since v2:
* Collect acked and reviewed-by tags from v1 that were
missed in v2
* Add comment and commit message suggestions from Suzuki
* Rebase onto next-20210510 (also applies to perf/core)
Thanks
James
James Clark (2):
perf cs-etm: Refactor timestamp variable names
perf cs-etm: Set time on synthesised samples to preserve ordering
.../perf/util/cs-etm-decoder/cs-etm-decoder.c | 18 +++---
tools/perf/util/cs-etm.c | 57 +++++++++++--------
tools/perf/util/cs-etm.h | 4 +-
3 files changed, 44 insertions(+), 35 deletions(-)
--
2.28.0
next reply other threads:[~2021-05-10 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:32 James Clark [this message]
2021-05-10 14:32 ` [PATCH v3 1/2] perf cs-etm: Refactor timestamp variable names James Clark
2021-05-11 15:36 ` Mathieu Poirier
2021-05-10 14:32 ` [PATCH v3 2/2] perf cs-etm: Set time on synthesised samples to preserve ordering James Clark
2021-05-11 15:37 ` [PATCH v3 0/2] " Mathieu Poirier
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=20210510143248.27423-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=al.grant@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=branislav.rankov@arm.com \
--cc=coresight@lists.linaro.org \
--cc=denik@chromium.org \
--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=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=suzuki.poulose@arm.com \
--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