From: Dongli Zhang <dongli.zhang@oracle.com>
To: Like Xu <like.xu.linux@gmail.com>
Cc: pbonzini@redhat.com, peter.maydell@linaro.org,
mtosatti@redhat.com, chenhuacai@kernel.org, philmd@linaro.org,
aurelien@aurel32.net, jiaxun.yang@flygoat.com,
aleksandar.rikalo@syrmia.com, danielhb413@gmail.com,
clg@kaod.org, david@gibson.dropbear.id.au, groug@kaod.org,
palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, pasic@linux.ibm.com,
borntraeger@linux.ibm.com, richard.henderson@linaro.org,
david@redhat.com, iii@linux.ibm.com, thuth@redhat.com,
joe.jin@oracle.com, qemu-s390x@nongnu.org, qemu-riscv@nongnu.org,
qemu-ppc@nongnu.org, qemu-arm@nongnu.org,
kvm list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] kvm: fix two svm pmu virtualization bugs
Date: Sun, 20 Nov 2022 23:38:15 -0800 [thread overview]
Message-ID: <c67e8d0f-95a5-a465-4b52-8ad6b78681c6@oracle.com> (raw)
In-Reply-To: <187668e7-f32e-b509-8ce1-4b35d98c7d31@gmail.com>
Hi Like,
On 11/20/22 22:42, Like Xu wrote:
> On 19/11/2022 8:28 pm, Dongli Zhang wrote:
>> This patchset is to fix two svm pmu virtualization bugs.
>>
>> 1. The 1st bug is that "-cpu,-pmu" cannot disable svm pmu virtualization.
>>
>> To use "-cpu EPYC" or "-cpu host,-pmu" cannot disable the pmu
>> virtualization. There is still below at the VM linux side ...
>
> Many QEMU vendor forks already have similar fixes, and
> thanks for bringing this issue back to the mainline.
Would you mind helping point to if there used to be any prior patchset for
mainline to resolve the issue?
>
>>
>> [ 0.510611] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
>>
>> ... although we expect something like below.
>>
>> [ 0.596381] Performance Events: PMU not available due to virtualization,
>> using software events only.
>> [ 0.600972] NMI watchdog: Perf NMI watchdog permanently disabled
>>
>> The patch 1-2 is to disable the pmu virtualization via KVM_PMU_CAP_DISABLE
>> if the per-vcpu "pmu" property is disabled.
>>
>> I considered 'KVM_X86_SET_MSR_FILTER' initially.
>> Since both KVM_X86_SET_MSR_FILTER and KVM_PMU_CAP_DISABLE are VM ioctl. I
>> finally used the latter because it is easier to use.
>>
>>
>> 2. The 2nd bug is that un-reclaimed perf events (after QEMU system_reset)
>> at the KVM side may inject random unwanted/unknown NMIs to the VM.
>>
>> The svm pmu registers are not reset during QEMU system_reset.
>>
>> (1). The VM resets (e.g., via QEMU system_reset or VM kdump/kexec) while it
>> is running "perf top". The pmu registers are not disabled gracefully.
>>
>> (2). Although the x86_cpu_reset() resets many registers to zero, the
>> kvm_put_msrs() does not puts AMD pmu registers to KVM side. As a result,
>> some pmu events are still enabled at the KVM side.
>>
>> (3). The KVM pmc_speculative_in_use() always returns true so that the events
>> will not be reclaimed. The kvm_pmc->perf_event is still active.
>
> I'm not sure if you're saying KVM doing something wrong, I don't think so
> because KVM doesn't sense the system_reset defined by QEME or other user space,
> AMD's vPMC will continue to be enabled (if it was enabled before), generating pmi
> injection into the guest, and the newly started guest doesn't realize the
> counter is still
> enabled and blowing up the error log.
I were not saying KVM was buggy.
I was trying to explain how the issue impacts KVM side and VM side.
>
>>
>> (4). After the reboot, the VM kernel reports below error:
>>
>> [ 0.092011] Performance Events: Fam17h+ core perfctr, Broken BIOS detected,
>> complain to your hardware vendor.
>> [ 0.092023] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR
>> c0010200 is 530076)
>>
>> (5). In a worse case, the active kvm_pmc->perf_event is still able to
>> inject unknown NMIs randomly to the VM kernel.
>>
>> [...] Uhhuh. NMI received for unknown reason 30 on CPU 0.
>>
>> The patch 3 is to fix the issue by resetting AMD pmu registers as well as
>> Intel registers.
>
> This fix idea looks good, it does require syncing the new changed device state
> of QEMU to KVM.
Thank you very much!
Dongli Zhang
>
>>
>>
>> This patchset does cover does not cover PerfMonV2, until the below patchset
>> is merged into the KVM side.
>>
>> [PATCH v3 0/8] KVM: x86: Add AMD Guest PerfMonV2 PMU support
>> https://lore.kernel.org/all/20221111102645.82001-1-likexu@tencent.com/
>>
>>
>> Dongli Zhang (3):
>> kvm: introduce a helper before creating the 1st vcpu
>> i386: kvm: disable KVM_CAP_PMU_CAPABILITY if "pmu" is disabled
>> target/i386/kvm: get and put AMD pmu registers
>>
>> accel/kvm/kvm-all.c | 7 ++-
>> include/sysemu/kvm.h | 2 +
>> target/arm/kvm64.c | 4 ++
>> target/i386/cpu.h | 5 +++
>> target/i386/kvm/kvm.c | 104 +++++++++++++++++++++++++++++++++++++++++++-
>> target/mips/kvm.c | 4 ++
>> target/ppc/kvm.c | 4 ++
>> target/riscv/kvm.c | 4 ++
>> target/s390x/kvm/kvm.c | 4 ++
>> 9 files changed, 134 insertions(+), 4 deletions(-)
>>
>> Thank you very much!
>>
>> Dongli Zhang
>>
>>
>>
prev parent reply other threads:[~2022-11-21 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:28 [PATCH 0/3] kvm: fix two svm pmu virtualization bugs Dongli Zhang
2022-11-19 12:28 ` [PATCH 1/3] kvm: introduce a helper before creating the 1st vcpu Dongli Zhang
2022-11-19 12:29 ` [PATCH 2/3] i386: kvm: disable KVM_CAP_PMU_CAPABILITY if "pmu" is disabled Dongli Zhang
2022-11-21 11:03 ` Greg Kurz
2022-11-21 14:23 ` Liang Yan
2022-11-21 21:11 ` Dongli Zhang
2023-11-13 16:39 ` Denis V. Lunev
2022-11-19 12:29 ` [PATCH 3/3] target/i386/kvm: get and put AMD pmu registers Dongli Zhang
2022-11-21 14:28 ` Liang Yan
2022-11-21 21:33 ` Dongli Zhang
2022-11-21 6:42 ` [PATCH 0/3] kvm: fix two svm pmu virtualization bugs Like Xu
2022-11-21 7:38 ` Dongli Zhang [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=c67e8d0f-95a5-a465-4b52-8ad6b78681c6@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=alistair.francis@wdc.com \
--cc=aurelien@aurel32.net \
--cc=bin.meng@windriver.com \
--cc=borntraeger@linux.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=groug@kaod.org \
--cc=iii@linux.ibm.com \
--cc=jiaxun.yang@flygoat.com \
--cc=joe.jin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=mtosatti@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.