From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Ian Rogers <irogers@google.com>
Cc: peterz@infradead.org, namhyung@kernel.org, eranian@google.com,
acme@kernel.org, mark.rutland@arm.com, jolsa@kernel.org,
bp@alien8.de, kan.liang@linux.intel.com, adrian.hunter@intel.com,
maddy@linux.ibm.com, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
sandipan.das@amd.com, ananth.narayan@amd.com,
santosh.shukla@amd.com, Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH v3 3/3] perf test: Add selftest to test IBS invocation via core pmu events
Date: Tue, 2 May 2023 08:38:10 +0530 [thread overview]
Message-ID: <90a2a0dd-62e1-93a2-6d8a-50c68823078b@amd.com> (raw)
In-Reply-To: <CAP-5=fVnfNEKK_UPuRprSVuCgQG-X-hCM6Jq3AKRHYfBiqisKw@mail.gmail.com>
On 30-Apr-23 2:39 AM, Ian Rogers wrote:
> On Tue, Apr 25, 2023 at 7:23 AM Ravi Bangoria <ravi.bangoria@amd.com> wrote:
>>
>> IBS pmu can be invoked via fixed set of core pmu events with 'precise_ip'
>> set to 1. Add a simple event open test for all these events.
>>
>> Without kernel fix:
>> $ sudo ./perf test -vv 76
>> 76: AMD IBS via core pmu :
>> --- start ---
>> test child forked, pid 6553
>> Using CPUID AuthenticAMD-25-1-1
>> type: 0x0, config: 0x0, fd: 3 - Pass
>> type: 0x0, config: 0x1, fd: -1 - Pass
>> type: 0x4, config: 0x76, fd: -1 - Fail
>> type: 0x4, config: 0xc1, fd: -1 - Fail
>> type: 0x4, config: 0x12, fd: -1 - Pass
>> test child finished with -1
>> ---- end ----
>> AMD IBS via core pmu: FAILED!
>>
>> With kernel fix:
>> $ sudo ./perf test -vv 76
>> 76: AMD IBS via core pmu :
>> --- start ---
>> test child forked, pid 7526
>> Using CPUID AuthenticAMD-25-1-1
>> type: 0x0, config: 0x0, fd: 3 - Pass
>> type: 0x0, config: 0x1, fd: -1 - Pass
>> type: 0x4, config: 0x76, fd: 3 - Pass
>> type: 0x4, config: 0xc1, fd: 3 - Pass
>> type: 0x4, config: 0x12, fd: -1 - Pass
>> test child finished with 0
>> ---- end ----
>> AMD IBS via core pmu: Ok
>>
>> Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com>
>
> Thanks Ravi, as the test is AMD specific I think it makes sense to place it in:
> tools/perf/arch/x86/tests
> and then to update the test list in:
> tools/perf/arch/x86/tests/arch-tests.c
Sure, will respin.
Thanks,
Ravi
prev parent reply other threads:[~2023-05-02 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 14:22 [PATCH v3 0/3] perf: Rework event forwarding logic Ravi Bangoria
2023-04-25 14:22 ` [PATCH v3 1/3] perf/core: Rework forwarding of {task|cpu}-clock events Ravi Bangoria
2023-05-02 15:34 ` Peter Zijlstra
2023-05-03 8:32 ` Ravi Bangoria
2023-04-25 14:22 ` [PATCH v3 2/3] perf/ibs: Fix interface via core pmu events Ravi Bangoria
2023-05-02 15:37 ` Peter Zijlstra
2023-05-03 8:33 ` Ravi Bangoria
2023-04-25 14:22 ` [PATCH v3 3/3] perf test: Add selftest to test IBS invocation " Ravi Bangoria
2023-04-29 21:09 ` Ian Rogers
2023-05-02 3:08 ` Ravi Bangoria [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=90a2a0dd-62e1-93a2-6d8a-50c68823078b@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=x86@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
all inboxes | Powered by JetHome®