From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: linux-perf-users@vger.kernel.org, Al.Grant@arm.com,
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@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Leo Yan <leo.yan@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org
Subject: Re: [PATCH 0/5] perf: cs-etm: Print auxtrace info even if OpenCSD isn't linked
Date: Mon, 12 Dec 2022 16:50:49 -0300 [thread overview]
Message-ID: <Y5eGGb28EAK43j26@kernel.org> (raw)
In-Reply-To: <20221212155513.2259623-1-james.clark@arm.com>
Em Mon, Dec 12, 2022 at 03:55:08PM +0000, James Clark escreveu:
> The auxtrace info header can be useful for debugging, and at the
> moment it's possible to record a file without OpenCSD linked but
> not view the header even though it should be possible to do.
>
> This patchset tidies up some of the related functions and
> improves some of the error messages before making the above
> possible in the last commit.
>
> Testing done:
>
> * Compiled on x86 and Arm both with and without CORESIGHT=1
> * Ran the Coresight tests
>
> Applies to perf/core (0c3852adae8)
Thanks, applied.
- Arnaldo
> James Clark (5):
> perf: cs-etm: Print unknown header version as an error
> perf: cs-etm: Remove unused stub methods
> perf: cs-etm: Tidy up auxtrace info header printing
> perf: cs-etm: Cleanup cs_etm__process_auxtrace_info()
> perf: cs-etm: Print auxtrace info even if OpenCSD isn't linked
>
> tools/perf/util/Build | 1 +
> tools/perf/util/cs-etm-base.c | 174 ++++++++++++++++++++++++++++
> tools/perf/util/cs-etm.c | 208 +++-------------------------------
> tools/perf/util/cs-etm.h | 46 ++------
> 4 files changed, 200 insertions(+), 229 deletions(-)
> create mode 100644 tools/perf/util/cs-etm-base.c
>
> --
> 2.25.1
--
- Arnaldo
prev parent reply other threads:[~2022-12-12 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 15:55 [PATCH 0/5] perf: cs-etm: Print auxtrace info even if OpenCSD isn't linked James Clark
2022-12-12 15:55 ` [PATCH 1/5] perf: cs-etm: Print unknown header version as an error James Clark
2022-12-12 15:55 ` [PATCH 2/5] perf: cs-etm: Remove unused stub methods James Clark
2022-12-12 15:55 ` [PATCH 3/5] perf: cs-etm: Tidy up auxtrace info header printing James Clark
2022-12-12 15:55 ` [PATCH 4/5] perf: cs-etm: Cleanup cs_etm__process_auxtrace_info() James Clark
2022-12-12 15:55 ` [PATCH 5/5] perf: cs-etm: Print auxtrace info even if OpenCSD isn't linked James Clark
2022-12-12 19:50 ` Arnaldo Carvalho de Melo [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=Y5eGGb28EAK43j26@kernel.org \
--to=acme@kernel.org \
--cc=Al.Grant@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).