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>
Cc: kernel test robot <oliver.sang@intel.com>,
	g@google.com, oe-lkp@lists.linux.dev, lkp@intel.com,
	Maxim Levitsky <mlevitsk@redhat.com>,
	kvm@vger.kernel.org, xudong.hao@intel.com
Subject: Re: [linux-next:master] [KVM] 7803339fa9: kernel-selftests.kvm.pmu_counters_test.fail
Date: Wed, 22 Jan 2025 09:26:24 +0800	[thread overview]
Message-ID: <2aa70d89-dd04-4b46-a7bd-01e21f010e3a@linux.intel.com> (raw)
In-Reply-To: <Z4_HvwSYX592oQ5s@google.com>


On 1/22/2025 12:13 AM, Sean Christopherson wrote:
> On Mon, Jan 20, 2025, Dapeng Mi wrote:
>> On 1/18/2025 1:11 AM, Sean Christopherson wrote:
>>> @@ -98,14 +149,12 @@ static uint8_t guest_get_pmu_version(void)
>>>   * Sanity check that in all cases, the event doesn't count when it's disabled,
>>>   * and that KVM correctly emulates the write of an arbitrary value.
>>>   */
>>> -static void guest_assert_event_count(uint8_t idx,
>>> -				     struct kvm_x86_pmu_feature event,
>>> -				     uint32_t pmc, uint32_t pmc_msr)
>>> +static void guest_assert_event_count(uint8_t idx, uint32_t pmc, uint32_t pmc_msr)
>>>  {
>>>  	uint64_t count;
>>>  
>>>  	count = _rdpmc(pmc);
>>> -	if (!this_pmu_has(event))
>>> +	if (!(hardware_pmu_arch_events & BIT(idx)))
>>>  		goto sanity_checks;
>>>  
>>>  	switch (idx) {
>>> @@ -126,7 +175,9 @@ static void guest_assert_event_count(uint8_t idx,
>>>  		GUEST_ASSERT_NE(count, 0);
>>>  		break;
>>>  	case INTEL_ARCH_TOPDOWN_SLOTS_INDEX:
>>> -		GUEST_ASSERT(count >= NUM_INSNS_RETIRED);
>>> +		__GUEST_ASSERT(count < NUM_INSNS_RETIRED,
>> shouldn't be "__GUEST_ASSERT(count >= NUM_INSNS_RETIRED," ?
> Yes.  I had intentionally inverted the check to verify the assert message and
> forgot to flip it back before hitting "send".  Thankfully, I didn't forget before
> posting formally[*].  Ugh, but I did forget to Cc you on that series, sorry :-/
>
> [*] https://lore.kernel.org/all/20250117234204.2600624-6-seanjc@google.com

Good to know. Thanks.


>

      reply	other threads:[~2025-01-22  1:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  2:40 [linux-next:master] [KVM] 7803339fa9: kernel-selftests.kvm.pmu_counters_test.fail kernel test robot
2025-01-14 19:47 ` Sean Christopherson
2025-01-15  2:44   ` Mi, Dapeng
2025-01-17  3:04     ` Mi, Dapeng
2025-01-17 17:11       ` Sean Christopherson
2025-01-20  2:02         ` Mi, Dapeng
2025-01-21 16:13           ` Sean Christopherson
2025-01-22  1:26             ` Mi, Dapeng [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=2aa70d89-dd04-4b46-a7bd-01e21f010e3a@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=g@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mlevitsk@redhat.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=seanjc@google.com \
    --cc=xudong.hao@intel.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