public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kan Liang <kan.liang@linux.intel.com>,
	Jim Mattson <jmattson@google.com>,
	Jinrong Liang <cloudliang@tencent.com>,
	Aaron Lewis <aaronlewis@google.com>, Like Xu <likexu@tencent.com>
Subject: Re: [PATCH v7 13/19] KVM: selftests: Add functional test for Intel's fixed PMU counters
Date: Thu, 9 Nov 2023 15:39:05 +0800	[thread overview]
Message-ID: <b62e34cc-2756-4d69-b75a-26919a3e0ef7@linux.intel.com> (raw)
In-Reply-To: <20231108003135.546002-14-seanjc@google.com>


On 11/8/2023 8:31 AM, Sean Christopherson wrote:
> From: Jinrong Liang <cloudliang@tencent.com>
>
> Extend the fixed counters test to verify that supported counters can
> actually be enabled in the control MSRs, that unsupported counters cannot,
> and that enabled counters actually count.
>
> Co-developed-by: Like Xu <likexu@tencent.com>
> Signed-off-by: Like Xu <likexu@tencent.com>
> Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
> [sean: fold into the rd/wr access test, massage changelog]
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
>   .../selftests/kvm/x86_64/pmu_counters_test.c  | 31 ++++++++++++++++++-
>   1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/pmu_counters_test.c b/tools/testing/selftests/kvm/x86_64/pmu_counters_test.c
> index 8c934e261f2d..b9c073d3ade9 100644
> --- a/tools/testing/selftests/kvm/x86_64/pmu_counters_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/pmu_counters_test.c
> @@ -324,7 +324,6 @@ static void guest_rd_wr_counters(uint32_t base_msr, uint8_t nr_possible_counters
>   		vector = wrmsr_safe(msr, 0);
>   		GUEST_ASSERT_PMC_MSR_ACCESS(WRMSR, msr, expect_gp, vector);
>   	}
> -	GUEST_DONE();
>   }
>   
>   static void guest_test_gp_counters(void)
> @@ -342,6 +341,7 @@ static void guest_test_gp_counters(void)
>   		base_msr = MSR_IA32_PERFCTR0;
>   
>   	guest_rd_wr_counters(base_msr, MAX_NR_GP_COUNTERS, nr_gp_counters, 0);
> +	GUEST_DONE();
>   }
>   
>   static void test_gp_counters(uint8_t pmu_version, uint64_t perf_capabilities,
> @@ -365,6 +365,7 @@ static void guest_test_fixed_counters(void)
>   {
>   	uint64_t supported_bitmask = 0;
>   	uint8_t nr_fixed_counters = 0;
> +	uint8_t i;
>   
>   	/* Fixed counters require Architectural vPMU Version 2+. */
>   	if (guest_get_pmu_version() >= 2)
> @@ -379,6 +380,34 @@ static void guest_test_fixed_counters(void)
>   
>   	guest_rd_wr_counters(MSR_CORE_PERF_FIXED_CTR0, MAX_NR_FIXED_COUNTERS,
>   			     nr_fixed_counters, supported_bitmask);
> +
> +	for (i = 0; i < MAX_NR_FIXED_COUNTERS; i++) {
> +		uint8_t vector;
> +		uint64_t val;
> +
> +		if (i >= nr_fixed_counters && !(supported_bitmask & BIT_ULL(i))) {
> +			vector = wrmsr_safe(MSR_CORE_PERF_FIXED_CTR_CTRL,
> +					    FIXED_PMC_CTRL(i, FIXED_PMC_KERNEL));
> +			__GUEST_ASSERT(vector == GP_VECTOR,
> +				       "Expected #GP for counter %u in FIXED_CTR_CTRL", i);
> +
> +			vector = wrmsr_safe(MSR_CORE_PERF_GLOBAL_CTRL,
> +					    FIXED_PMC_GLOBAL_CTRL_ENABLE(i));
> +			__GUEST_ASSERT(vector == GP_VECTOR,
> +				       "Expected #GP for counter %u in PERF_GLOBAL_CTRL", i);
> +			continue;
> +		}
> +
> +		wrmsr(MSR_CORE_PERF_FIXED_CTR0 + i, 0);
> +		wrmsr(MSR_CORE_PERF_FIXED_CTR_CTRL, FIXED_PMC_CTRL(i, FIXED_PMC_KERNEL));
> +		wrmsr(MSR_CORE_PERF_GLOBAL_CTRL, FIXED_PMC_GLOBAL_CTRL_ENABLE(i));
> +		__asm__ __volatile__("loop ." : "+c"((int){NUM_BRANCHES}));

This assembly code seems to be called many times, we may wrap it into a 
macro or function.

Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>


> +		wrmsr(MSR_CORE_PERF_GLOBAL_CTRL, 0);
> +		val = rdmsr(MSR_CORE_PERF_FIXED_CTR0 + i);
> +
> +		GUEST_ASSERT_NE(val, 0);
> +	}
> +	GUEST_DONE();
>   }
>   
>   static void test_fixed_counters(uint8_t pmu_version, uint64_t perf_capabilities,

  reply	other threads:[~2023-11-09  7:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  0:31 [PATCH v7 00/19] KVM: x86/pmu: selftests: Fixes and new tests Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 01/19] KVM: x86/pmu: Always treat Fixed counters as available when supported Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 02/19] KVM: x86/pmu: Allow programming events that match unsupported arch events Sean Christopherson
2023-11-08  1:24   ` Jim Mattson
2023-11-08 20:41   ` Liang, Kan
2023-11-08  0:31 ` [PATCH v7 03/19] KVM: x86/pmu: Remove KVM's enumeration of Intel's architectural encodings Sean Christopherson
2023-11-08 16:06   ` Liang, Kan
2023-11-08 19:35     ` Sean Christopherson
2023-11-08 20:38       ` Liang, Kan
2023-11-08  0:31 ` [PATCH v7 04/19] KVM: x86/pmu: Setup fixed counters' eventsel during PMU initialization Sean Christopherson
2023-11-08  1:28   ` Jim Mattson
2023-11-08 14:39     ` Sean Christopherson
2023-11-08 19:00       ` Jim Mattson
2023-11-08  0:31 ` [PATCH v7 05/19] KVM: selftests: Add vcpu_set_cpuid_property() to set properties Sean Christopherson
2023-11-08 19:11   ` Jim Mattson
2023-11-08  0:31 ` [PATCH v7 06/19] KVM: selftests: Drop the "name" param from KVM_X86_PMU_FEATURE() Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 07/19] KVM: selftests: Extend {kvm,this}_pmu_has() to support fixed counters Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 08/19] KVM: selftests: Add pmu.h and lib/pmu.c for common PMU assets Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 09/19] KVM: selftests: Test Intel PMU architectural events on gp counters Sean Christopherson
2023-11-09  7:28   ` Mi, Dapeng
2023-11-08  0:31 ` [PATCH v7 10/19] KVM: selftests: Test Intel PMU architectural events on fixed counters Sean Christopherson
2023-11-09  7:30   ` Mi, Dapeng
2023-11-09 15:23   ` Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 11/19] KVM: selftests: Test consistency of CPUID with num of gp counters Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 12/19] KVM: selftests: Test consistency of CPUID with num of fixed counters Sean Christopherson
2023-11-09  7:34   ` Mi, Dapeng
2023-11-09 15:19     ` Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 13/19] KVM: selftests: Add functional test for Intel's fixed PMU counters Sean Christopherson
2023-11-09  7:39   ` Mi, Dapeng [this message]
2023-11-08  0:31 ` [PATCH v7 14/19] KVM: selftests: Expand PMU counters test to verify LLC events Sean Christopherson
2023-11-09  7:43   ` Mi, Dapeng
2023-11-08  0:31 ` [PATCH v7 15/19] KVM: selftests: Add a helper to query if the PMU module param is enabled Sean Christopherson
2023-11-09  7:45   ` Mi, Dapeng
2023-11-08  0:31 ` [PATCH v7 16/19] KVM: selftests: Add helpers to read integer module params Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 17/19] KVM: selftests: Query module param to detect FEP in MSR filtering test Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 18/19] KVM: selftests: Move KVM_FEP macro into common library header Sean Christopherson
2023-11-08  0:31 ` [PATCH v7 19/19] KVM: selftests: Test PMC virtualization with forced emulation Sean Christopherson
2023-11-09  7:51   ` Mi, Dapeng

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=b62e34cc-2756-4d69-b75a-26919a3e0ef7@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=aaronlewis@google.com \
    --cc=cloudliang@tencent.com \
    --cc=jmattson@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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