Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Sandipan Das <sandipan.das@amd.com>
To: zhao1.liu@intel.com, Dongli Zhang <dongli.zhang@oracle.com>
Cc: pbonzini@redhat.com, mtosatti@redhat.com, babu.moger@amd.com,
	likexu@tencent.com, like.xu.linux@gmail.com, groug@kaod.org,
	khorenko@virtuozzo.com, alexander.ivanov@virtuozzo.com,
	den@virtuozzo.com, davydov-max@yandex-team.ru,
	xiaoyao.li@intel.com, dapeng1.mi@linux.intel.com,
	joe.jin@oracle.com, ewanhai-oc@zhaoxin.com, ewanhai@zhaoxin.com,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v8 1/7] target/i386/kvm: set KVM_PMU_CAP_DISABLE if "-pmu" is configured
Date: Tue, 6 Oct 2026 14:11:05 +0530	[thread overview]
Message-ID: <84b5b038-e32f-4765-9d23-9f6ecbf382c0@amd.com> (raw)
In-Reply-To: <502e4c1f-3f5a-462d-87c3-076612935784@amd.com>

On 01-10-2026 16:42, Sandipan Das wrote:
> On 01-10-2026 16:35, Michael Tokarev wrote:
>> On 10/1/26 13:43, Sandipan Das wrote:
>>> On 01-10-2026 15:30, Michael Tokarev wrote:
>>>> On 10/1/26 11:54, Sandipan Das wrote:
>>>>> On 01-10-2026 14:02, Michael Tokarev wrote:
>>>> ...
>>>>
>>>>>> When booting windows11 VM with -cpu EPYC-Rome-v4 -enable-kvm, the
>>>>>> guest enters tight CPU loop while displaying a boot screen, before
>>>>>> it starts showing up the rotating circle (which shows boot progress).
>>>>
>>>>
>>>>> What happens if you use "-cpu EPYC-Rome-v4,+pmu"?
>>>>
>>>> With that, it boots fine, just like before this patch.
>>>> I checked current master too - same, +pmu fixes it.
>>>>
>>> A guest OS cannot expect a functioning PMU if the hypervisor has disabled
>>> it. Linux runs a basic sanity test to determine this. See:
>>> https://github.com/torvalds/linux/blob/master/arch/x86/events/core.c#L268
>>
>> So.. what do we do with all this?  :)
>>
>> I kinda see the intention of the original change, but it results in
>> non-bootable systems (linux too, as I think you demonstrate above).
>>
> 
> Because of the sanity test, Linux will boot but not register the "cpu" PMU.
> Perhaps others should also run a similar sanity test on PMU hardware rather
> than making assumptions and failing to boot.

After looking at kvm_msr and kvm_cpuid traces, I see that Windows is indeed
getting #GPs upon accessing MSRs 0xc0010200 and 0xc0010201 but it is not at
fault here since it expects these MSRs to be available as guest CPUID
0x80000001[ECX].PerfCtrExtCore is set. This feature bit should have been
cleared by QEMU when "pmu=off".

It boots up when "pmu=off" is combined with "perfctr-core=off" and
"perfmon-v2=off". The missing pieces here are the following:

https://lore.kernel.org/qemu-devel/20251111061532.36702-2-dongli.zhang@oracle.com/
https://lore.kernel.org/qemu-devel/20251111061532.36702-3-dongli.zhang@oracle.com/

Dongli, Zhao,

I see a discussion about compat array at
https://lore.kernel.org/qemu-devel/aUEXkDDOba+oZ4v+@intel.com/

Is this ready for the two patches above to be pulled in?

  reply	other threads:[~2026-10-06  8:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  7:42 [PATCH v8 0/7] target/i386/kvm/pmu: PMU Enhancement, Bugfix and Cleanup Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 1/7] target/i386/kvm: set KVM_PMU_CAP_DISABLE if "-pmu" is configured Dongli Zhang
2026-10-01  8:32   ` Michael Tokarev
2026-10-01  8:54     ` Sandipan Das
2026-10-01 10:00       ` Michael Tokarev
2026-10-01 10:43         ` Sandipan Das
2026-10-01 11:05           ` Michael Tokarev
2026-10-01 11:12             ` Sandipan Das
2026-10-06  8:41               ` Sandipan Das [this message]
2026-10-07  0:51                 ` Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 2/7] target/i386/kvm: extract unrelated code out of kvm_x86_build_cpuid() Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 3/7] target/i386/kvm: rename architectural PMU variables Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 4/7] target/i386/kvm: query kvm.enable_pmu parameter Dongli Zhang
2026-01-02 22:59   ` Chen, Zide
2026-01-05 20:21     ` Dongli Zhang
2026-01-06 21:03       ` Chen, Zide
2026-01-07  8:05         ` Dongli Zhang
2026-01-07 18:09           ` Chen, Zide
2025-12-30  7:42 ` [PATCH v8 5/7] target/i386/kvm: reset AMD PMU registers during VM reset Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 6/7] target/i386/kvm: support perfmon-v2 for reset Dongli Zhang
2025-12-30  7:42 ` [PATCH v8 7/7] target/i386/kvm: don't stop Intel PMU counters Dongli Zhang
2026-01-03  0:27   ` Chen, Zide
2026-01-05 20:24     ` Dongli Zhang
2026-01-06 21:04       ` Chen, Zide
2026-01-07  8:36         ` Dongli Zhang

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=84b5b038-e32f-4765-9d23-9f6ecbf382c0@amd.com \
    --to=sandipan.das@amd.com \
    --cc=alexander.ivanov@virtuozzo.com \
    --cc=babu.moger@amd.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=davydov-max@yandex-team.ru \
    --cc=den@virtuozzo.com \
    --cc=dongli.zhang@oracle.com \
    --cc=ewanhai-oc@zhaoxin.com \
    --cc=ewanhai@zhaoxin.com \
    --cc=groug@kaod.org \
    --cc=joe.jin@oracle.com \
    --cc=khorenko@virtuozzo.com \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=likexu@tencent.com \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoyao.li@intel.com \
    --cc=zhao1.liu@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