From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org, irogers@google.com
Cc: James Clark <james.clark@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Leo Yan <leo.yan@linux.dev>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] perf test: "object code reading" test fixes
Date: Tue, 9 Apr 2024 09:47:36 +0100 [thread overview]
Message-ID: <20240409084741.405433-1-james.clark@arm.com> (raw)
A few fixes around the object code reading test. The third patch
appears to be unrelated, but in this case the data symbol test was
broken on Arm N1 by the first commit.
James Clark (3):
perf tests: Apply attributes to all events in object code reading test
perf map: Remove kernel map before updating start and end addresses
perf tests: Skip "test data symbol" on Neoverse N1
tools/perf/tests/code-reading.c | 10 +++++-----
tools/perf/tests/shell/test_data_symbol.sh | 6 ++++++
tools/perf/util/machine.c | 2 +-
3 files changed, 12 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-09 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 8:47 James Clark [this message]
2024-04-09 8:47 ` [PATCH 1/3] perf tests: Apply attributes to all events in object code reading test James Clark
2024-04-09 8:47 ` [PATCH 2/3] perf map: Remove kernel map before updating start and end addresses James Clark
2024-04-09 8:47 ` [PATCH 3/3] perf tests: Skip "test data symbol" on Neoverse N1 James Clark
2024-04-09 15:39 ` Ian Rogers
2024-04-09 23:17 ` Namhyung Kim
2024-04-10 9:07 ` James Clark
2024-04-10 9:08 ` James Clark
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=20240409084741.405433-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®