From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
oliver.sang@intel.com, Like Xu <like.xu@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] KVM: x86: Fix MSR_IA32_PERF_CAPABILITIES writes check and vmx_pmu_msrs_test
Date: Thu, 16 Dec 2021 17:52:11 +0100 [thread overview]
Message-ID: <20211216165213.338923-1-vkuznets@redhat.com> (raw)
This is a continuation of "KVM: selftests: Avoid KVM_SET_CPUID2 after
KVM_RUN in vmx_pmu_msrs_test" work. Instead of fixing the immediate issue,
drop incorrect check in KVM which was making the result of host initiated
writes to MSR_IA32_PERF_CAPABILITIES dependent on guest visible CPUIDs and
the corresponding tests in vmx_pmu_msrs_test, this will also make the issue
reported by kernel test robot to go away.
Vitaly Kuznetsov (2):
KVM: selftests: vmx_pmu_msrs_test: Drop tests mangling guest visible
CPUIDs
KVM: x86: Drop guest CPUID check for host initiated writes to
MSR_IA32_PERF_CAPABILITIES
arch/x86/kvm/x86.c | 2 +-
.../selftests/kvm/x86_64/vmx_pmu_msrs_test.c | 17 -----------------
2 files changed, 1 insertion(+), 18 deletions(-)
--
2.33.1
next reply other threads:[~2021-12-16 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:52 Vitaly Kuznetsov [this message]
2021-12-16 16:52 ` [PATCH v2 1/2] KVM: selftests: vmx_pmu_msrs_test: Drop tests mangling guest visible CPUIDs Vitaly Kuznetsov
2021-12-16 16:52 ` [PATCH v2 2/2] KVM: x86: Drop guest CPUID check for host initiated writes to MSR_IA32_PERF_CAPABILITIES Vitaly Kuznetsov
2021-12-19 19:24 ` [PATCH v2 0/2] KVM: x86: Fix MSR_IA32_PERF_CAPABILITIES writes check and vmx_pmu_msrs_test Paolo Bonzini
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=20211216165213.338923-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@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
all inboxes | Powered by JetHome®