From: Shaoqin Huang <shahuang@redhat.com>
To: Eric Auger <eauger@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev
Cc: James Morse <james.morse@arm.com>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v3 0/5] KVM: selftests: aarch64: Introduce pmu_event_filter_test
Date: Wed, 31 Jan 2024 11:11:28 +0800 [thread overview]
Message-ID: <d2d09269-30fa-461d-9461-16a1ffbde6b6@redhat.com> (raw)
In-Reply-To: <51ca8edc-81e6-4c6d-9c72-80fe59919868@redhat.com>
Hi Eric,
On 1/26/24 18:25, Eric Auger wrote:
> Hi Shaoqin,
>
> On 1/16/24 07:01, Shaoqin Huang wrote:
>> The test is inspired by the pmu_event_filter_test which implemented by x86. On
>> the arm64 platform, there is the same ability to set the pmu_event_filter
>> through the KVM_ARM_VCPU_PMU_V3_FILTER attribute. So add the test for arm64.
>>
>> The series first move some pmu common code from vpmu_counter_access to
>> lib/aarch64/vpmu.c and include/aarch64/vpmu.h, which can be used by
>> pmu_event_filter_test. Then fix a bug related to the [enable|disable]_counter,
>> and at last, implement the test itself.
> which branch does it apply on? I fail to apply on top on main.
>
> Or can you provide a branch?
This was based on v6.7.
>
> Eric
>>
>> Changelog:
>> ----------
>> v2->v3:
>> - Check the pmceid in guest code instead of pmu event count since different
>> hardware may have different event count result, check pmceid makes it stable
>> on different platform. [Eric]
>> - Some typo fixed and commit message improved.
>>
>> v1->v2:
>> - Improve the commit message. [Eric]
>> - Fix the bug in [enable|disable]_counter. [Raghavendra & Marc]
>> - Add the check if kvm has attr KVM_ARM_VCPU_PMU_V3_FILTER.
>> - Add if host pmu support the test event throught pmceid0.
>> - Split the test_invalid_filter() to another patch. [Eric]
>>
>> v1: https://lore.kernel.org/all/20231123063750.2176250-1-shahuang@redhat.com/
>> v2: https://lore.kernel.org/all/20231129072712.2667337-1-shahuang@redhat.com/
>>
>> Shaoqin Huang (5):
>> KVM: selftests: aarch64: Make the [create|destroy]_vpmu_vm() public
>> KVM: selftests: aarch64: Move pmu helper functions into vpmu.h
>> KVM: selftests: aarch64: Fix the buggy [enable|disable]_counter
>> KVM: selftests: aarch64: Introduce pmu_event_filter_test
>> KVM: selftests: aarch64: Add invalid filter test in
>> pmu_event_filter_test
>>
>> tools/testing/selftests/kvm/Makefile | 2 +
>> .../kvm/aarch64/pmu_event_filter_test.c | 255 ++++++++++++++++++
>> .../kvm/aarch64/vpmu_counter_access.c | 218 ++-------------
>> .../selftests/kvm/include/aarch64/vpmu.h | 135 ++++++++++
>> .../testing/selftests/kvm/lib/aarch64/vpmu.c | 74 +++++
>> 5 files changed, 490 insertions(+), 194 deletions(-)
>> create mode 100644 tools/testing/selftests/kvm/aarch64/pmu_event_filter_test.c
>> create mode 100644 tools/testing/selftests/kvm/include/aarch64/vpmu.h
>> create mode 100644 tools/testing/selftests/kvm/lib/aarch64/vpmu.c
>>
>
--
Shaoqin
prev parent reply other threads:[~2024-01-31 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 6:01 [PATCH v3 0/5] KVM: selftests: aarch64: Introduce pmu_event_filter_test Shaoqin Huang
2024-01-16 6:01 ` [PATCH v3 1/5] KVM: selftests: aarch64: Make the [create|destroy]_vpmu_vm() public Shaoqin Huang
2024-01-16 6:01 ` [PATCH v3 2/5] KVM: selftests: aarch64: Move pmu helper functions into vpmu.h Shaoqin Huang
2024-01-16 6:01 ` [PATCH v3 3/5] KVM: selftests: aarch64: Fix the buggy [enable|disable]_counter Shaoqin Huang
2024-01-16 6:01 ` [PATCH v3 4/5] KVM: selftests: aarch64: Introduce pmu_event_filter_test Shaoqin Huang
2024-01-16 6:01 ` [PATCH v3 5/5] KVM: selftests: aarch64: Add invalid filter test in pmu_event_filter_test Shaoqin Huang
2024-01-26 10:25 ` [PATCH v3 0/5] KVM: selftests: aarch64: Introduce pmu_event_filter_test Eric Auger
2024-01-31 3:11 ` Shaoqin Huang [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=d2d09269-30fa-461d-9461-16a1ffbde6b6@redhat.com \
--to=shahuang@redhat.com \
--cc=eauger@redhat.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.com \
/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).