From: Isaku Yamahata <isaku.yamahata@gmail.com>
To: Jinrong Liang <ljr.kernel@gmail.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>, Shuah Khan <shuah@kernel.org>,
Aaron Lewis <aaronlewis@google.com>,
David Matlack <dmatlack@google.com>,
Vishal Annapurve <vannapurve@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Like Xu <like.xu.linux@gmail.com>,
Jinrong Liang <cloudliang@tencent.com>,
linux-kselftest@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, isaku.yamahata@gmail.com
Subject: Re: [PATCH v4 4/6] KVM: selftests: Add test cases for unsupported PMU event filter input values
Date: Tue, 18 Jul 2023 18:17:52 -0700 [thread overview]
Message-ID: <20230719011752.GD25699@ls.amr.corp.intel.com> (raw)
In-Reply-To: <20230717062343.3743-5-cloudliang@tencent.com>
On Mon, Jul 17, 2023 at 02:23:41PM +0800,
Jinrong Liang <ljr.kernel@gmail.com> wrote:
> From: Jinrong Liang <cloudliang@tencent.com>
>
> Add test cases to verify the handling of unsupported input values for the
> PMU event filter. The tests cover unsupported "action" values, unsupported
> "flags" values, and unsupported "nevents" values. All these cases should
> return an error, as they are currently not supported by the filter.
> Furthermore, the tests also cover the scenario where setting non-existent
> fixed counters in the fixed bitmap does not fail.
>
> Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
> ---
> .../kvm/x86_64/pmu_event_filter_test.c | 26 +++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c b/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> index ffcbbf25b29b..63f85f583ef8 100644
> --- a/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> @@ -32,6 +32,10 @@
> #define MAX_FILTER_EVENTS 300
> #define MAX_TEST_EVENTS 10
>
> +#define PMU_EVENT_FILTER_INVALID_ACTION (KVM_PMU_EVENT_DENY + 1)
> +#define PMU_EVENT_FILTER_INVALID_FLAGS (KVM_PMU_EVENT_FLAG_MASKED_EVENTS + 1)
flag is a bit mask. Not number. So +1 sounds weird.
As KVM_PMU_EVENT_FLAGS_VALID_MASK = 1, this happens to get wanted result, though.
> +#define PMU_EVENT_FILTER_INVALID_NEVENTS (MAX_FILTER_EVENTS + 1)
> +
> /*
> * This is how the event selector and unit mask are stored in an AMD
> * core performance event-select register. Intel's format is similar,
> @@ -757,6 +761,8 @@ static int set_pmu_single_event_filter(struct kvm_vcpu *vcpu, uint64_t event,
>
> static void test_filter_ioctl(struct kvm_vcpu *vcpu)
> {
> + uint8_t nr_fixed_counters = kvm_cpu_property(X86_PROPERTY_PMU_NR_FIXED_COUNTERS);
> + struct __kvm_pmu_event_filter f;
> uint64_t e = ~0ul;
> int r;
>
> @@ -777,6 +783,26 @@ static void test_filter_ioctl(struct kvm_vcpu *vcpu)
> KVM_PMU_EVENT_FLAG_MASKED_EVENTS,
> KVM_PMU_EVENT_ALLOW);
> TEST_ASSERT(r == 0, "Valid PMU Event Filter is failing");
> +
> + f = base_event_filter;
> + f.action = PMU_EVENT_FILTER_INVALID_ACTION;
> + r = do_vcpu_set_pmu_event_filter(vcpu, &f);
> + TEST_ASSERT(r, "Set invalid action is expected to fail");
> +
> + f = base_event_filter;
> + f.flags = PMU_EVENT_FILTER_INVALID_FLAGS;
> + r = do_vcpu_set_pmu_event_filter(vcpu, &f);
> + TEST_ASSERT(r, "Set invalid flags is expected to fail");
> +
> + f = base_event_filter;
> + f.nevents = PMU_EVENT_FILTER_INVALID_NEVENTS;
> + r = do_vcpu_set_pmu_event_filter(vcpu, &f);
> + TEST_ASSERT(r, "Exceeding the max number of filter events should fail");
> +
> + f = base_event_filter;
> + f.fixed_counter_bitmap = ~GENMASK_ULL(nr_fixed_counters, 0);
> + r = do_vcpu_set_pmu_event_filter(vcpu, &f);
> + TEST_ASSERT(!r, "Masking non-existent fixed counters should be allowed");
> }
>
> int main(int argc, char *argv[])
> --
> 2.39.3
>
--
Isaku Yamahata <isaku.yamahata@gmail.com>
next prev parent reply other threads:[~2023-07-19 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 6:23 [PATCH v4 0/6] KVM: selftests: Improve PMU event filter settings and add test cases Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 1/6] KVM: selftests: Add macros for fixed counters in processor.h Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 2/6] KVM: selftests: Drop the return of remove_event() Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 3/6] KVM: selftests: Introduce __kvm_pmu_event_filter to improved event filter settings Jinrong Liang
2023-07-19 0:02 ` Isaku Yamahata
2023-07-19 3:26 ` Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 4/6] KVM: selftests: Add test cases for unsupported PMU event filter input values Jinrong Liang
2023-07-19 1:17 ` Isaku Yamahata [this message]
2023-07-19 3:20 ` Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 5/6] KVM: selftests: Test if event filter meets expectations on fixed counters Jinrong Liang
2023-07-19 1:21 ` Isaku Yamahata
2023-07-19 2:59 ` Jinrong Liang
2023-07-17 6:23 ` [PATCH v4 6/6] KVM: selftests: Test gp event filters don't affect fixed event filters Jinrong Liang
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=20230719011752.GD25699@ls.amr.corp.intel.com \
--to=isaku.yamahata@gmail.com \
--cc=aaronlewis@google.com \
--cc=cloudliang@tencent.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ljr.kernel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=vannapurve@google.com \
--cc=wanpengli@tencent.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).