From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Zeng Guang <guang.zeng@intel.com>, Chao Gao <chao.gao@intel.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH 00/11] KVM: x86: Prep work for VMX IPI virtualization
Date: Thu, 24 Feb 2022 15:58:50 +0100 [thread overview]
Message-ID: <a0594849-c141-16b5-4420-167174f2b2f1@redhat.com> (raw)
In-Reply-To: <20220204214205.3306634-1-seanjc@google.com>
On 2/4/22 22:41, Sean Christopherson wrote:
> Prepare for VMX's IPI virtualization, in which hardware treats ICR as a
> single 64-bit register in x2APIC mode. The SDM wasn't clear on how ICR
> should be modeled, KVM just took the easier path and guessed wrong.
>
> Hardware's implementation of ICR as a 64-bit register requires explicit
> handling to maintain backwards compatibility in KVM_{G,S}ET_REG, as
> migrating a VM between hosts with different IPI virtualization support
> would lead to ICR "corruption" for writes that aren't intercepted by
> KVM (hardware doesn't fill ICR2 in vAPIC page).
>
> This series includes AVIC cleanups for things I encountered along the way.
> AVIC still has multiple issues, this only fixes the easy bugs.
>
> Sean Christopherson (11):
> Revert "svm: Add warning message for AVIC IPI invalid target"
> KVM: VMX: Handle APIC-write offset wrangling in VMX code
> KVM: x86: Use "raw" APIC register read for handling APIC-write VM-Exit
> KVM: SVM: Use common kvm_apic_write_nodecode() for AVIC write traps
> KVM: SVM: Don't rewrite guest ICR on AVIC IPI virtualization failure
> KVM: x86: WARN if KVM emulates an IPI without clearing the BUSY flag
> KVM: x86: Make kvm_lapic_reg_{read,write}() static
> KVM: x86: Add helpers to handle 64-bit APIC MSR read/writes
> KVM: x86: Treat x2APIC's ICR as a 64-bit register, not two 32-bit regs
> KVM: x86: Make kvm_lapic_set_reg() a "private" xAPIC helper
> KVM: selftests: Add test to verify KVM handles x2APIC ICR=>ICR2 dance
>
> arch/x86/kvm/lapic.c | 193 ++++++++++++------
> arch/x86/kvm/lapic.h | 21 +-
> arch/x86/kvm/svm/avic.c | 38 ++--
> arch/x86/kvm/trace.h | 6 +-
> arch/x86/kvm/vmx/vmx.c | 11 +-
> arch/x86/kvm/x86.c | 15 +-
> tools/testing/selftests/kvm/.gitignore | 1 +
> tools/testing/selftests/kvm/Makefile | 1 +
> .../selftests/kvm/include/x86_64/apic.h | 1 +
> .../selftests/kvm/x86_64/xapic_state_test.c | 150 ++++++++++++++
> 10 files changed, 325 insertions(+), 112 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/x86_64/xapic_state_test.c
>
>
> base-commit: 17179d0068b20413de2355f84c75a93740257e20
Queued, with patch 4 adjusted. Thanks,
Paolo
prev parent reply other threads:[~2022-02-24 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 21:41 Sean Christopherson
2022-02-04 21:41 ` [PATCH 01/11] Revert "svm: Add warning message for AVIC IPI invalid target" Sean Christopherson
2022-02-07 16:44 ` Paolo Bonzini
2022-02-04 21:41 ` [PATCH 02/11] KVM: VMX: Handle APIC-write offset wrangling in VMX code Sean Christopherson
2022-02-15 2:22 ` Chao Gao
2022-02-15 16:30 ` Sean Christopherson
2022-02-04 21:41 ` [PATCH 03/11] KVM: x86: Use "raw" APIC register read for handling APIC-write VM-Exit Sean Christopherson
2022-02-04 21:41 ` [PATCH 04/11] KVM: SVM: Use common kvm_apic_write_nodecode() for AVIC write traps Sean Christopherson
2022-02-04 23:14 ` kernel test robot
2022-02-07 16:16 ` Sean Christopherson
2022-02-04 21:41 ` [PATCH 05/11] KVM: SVM: Don't rewrite guest ICR on AVIC IPI virtualization failure Sean Christopherson
2022-02-04 21:42 ` [PATCH 06/11] KVM: x86: WARN if KVM emulates an IPI without clearing the BUSY flag Sean Christopherson
2022-02-04 21:42 ` [PATCH 07/11] KVM: x86: Make kvm_lapic_reg_{read,write}() static Sean Christopherson
2022-02-04 21:42 ` [PATCH 08/11] KVM: x86: Add helpers to handle 64-bit APIC MSR read/writes Sean Christopherson
2022-02-04 21:42 ` [PATCH 09/11] KVM: x86: Treat x2APIC's ICR as a 64-bit register, not two 32-bit regs Sean Christopherson
2022-02-15 3:27 ` Chao Gao
2022-02-15 16:40 ` Sean Christopherson
2022-02-04 21:42 ` [PATCH 10/11] KVM: x86: Make kvm_lapic_set_reg() a "private" xAPIC helper Sean Christopherson
2022-02-04 21:42 ` [PATCH 11/11] KVM: selftests: Add test to verify KVM handles x2APIC ICR=>ICR2 dance Sean Christopherson
2022-02-24 14:58 ` Paolo Bonzini [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=a0594849-c141-16b5-4420-167174f2b2f1@redhat.com \
--to=pbonzini@redhat.com \
--cc=chao.gao@intel.com \
--cc=guang.zeng@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.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®