From: James Clark <james.clark@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
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>,
Anshuman Khandual <anshuman.khandual@arm.com>,
"Rob Herring (Arm)" <robh@kernel.org>,
Adam Young <admiyo@os.amperecomputing.com>,
Will Deacon <will@kernel.org>,
German Gomez <german.gomez@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 0/3] perf test: Extend branch stack sampling test for arm64 BRBE
Date: Wed, 1 Oct 2025 14:49:08 +0100 [thread overview]
Message-ID: <6baf0f01-a333-4bca-b39d-d01f8624e170@linaro.org> (raw)
In-Reply-To: <CAP-5=fXdFQCgeF5DRH=-cUErz2opU98H6u1cTTO3ZPJ7SMQfMw@mail.gmail.com>
On 18/08/2025 10:38 pm, Ian Rogers wrote:
> On Wed, Aug 13, 2025 at 6:39 AM James Clark <james.clark@linaro.org> wrote:
>>
>> Refactor and add some extra tests for all platforms which were useful
>> when developing and testing the BRBE (Branch Buffer Extension) driver
>> [1]. Then lastly extend the test for new features which are BRBE
>> specific.
>>
>> Tested on the Arm FVP RevC model [2] and Intel Raptor Lake.
>>
>> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58074a0fce66
>> [2]: https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms
>>
>> Signed-off-by: James Clark <james.clark@linaro.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
>
> Thanks,
> Ian
>
Hi Arnaldo,
If you have a chance can you take this one please. It still applies
cleanly to perf-tools-next.
Thanks
James
>> ---
>> James Clark (3):
>> perf test: Refactor brstack test
>> perf test: Add syscall and address tests to brstack test
>> perf test: Extend branch stack sampling test for Arm64 BRBE
>>
>> tools/perf/tests/builtin-test.c | 1 +
>> tools/perf/tests/shell/test_brstack.sh | 106 ++++++++++++++++++++++++++++++---
>> tools/perf/tests/tests.h | 1 +
>> tools/perf/tests/workloads/Build | 2 +
>> tools/perf/tests/workloads/traploop.c | 31 ++++++++++
>> 5 files changed, 132 insertions(+), 9 deletions(-)
>> ---
>> base-commit: 6235ce77749f45cac27f630337e2fdf04e8a6c73
>> change-id: 20250811-james-brbe-test-f5a20dffd734
>>
>> Best regards,
>> --
>> James Clark <james.clark@linaro.org>
>>
next prev parent reply other threads:[~2025-10-01 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 13:38 [PATCH 0/3] perf test: Extend branch stack sampling test for arm64 BRBE James Clark
2025-08-13 13:38 ` [PATCH 1/3] perf test: Refactor brstack test James Clark
2025-08-13 13:38 ` [PATCH 2/3] perf test: Add syscall and address tests to " James Clark
2025-08-13 13:38 ` [PATCH 3/3] perf test: Extend branch stack sampling test for Arm64 BRBE James Clark
2025-08-18 21:38 ` [PATCH 0/3] perf test: Extend branch stack sampling test for arm64 BRBE Ian Rogers
2025-10-01 13:49 ` James Clark [this message]
2025-10-01 18:32 ` Arnaldo Carvalho de Melo
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=6baf0f01-a333-4bca-b39d-d01f8624e170@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=admiyo@os.amperecomputing.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=german.gomez@arm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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 \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).