From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
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,
Wanpeng Li <kernellwp@gmail.com>,
Lai Jiangshan <laijs@linux.alibaba.com>
Subject: [PATCH 0/2] KVM: VMX: Revert back to refreshing HOST_CR3 at ->run
Date: Thu, 24 Feb 2022 19:19:15 +0000 [thread overview]
Message-ID: <20220224191917.3508476-1-seanjc@google.com> (raw)
Revert back to refreshing vmcs.HOST_CR3 in vmx_vcpu_run(), the PCID in
CR3 can be bumped in KVM context if KVM triggers code patching of any
kind, e.g. when updating the apic_hw_disabled static key in response to
a WRMSR(APIC_BASE).
Sean Christopherson (2):
Revert "KVM: VMX: Save HOST_CR3 in vmx_set_host_fs_gs()"
Revert "KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()"
arch/x86/kvm/vmx/nested.c | 11 ++++++++---
arch/x86/kvm/vmx/vmx.c | 28 +++++++++++++++++-----------
arch/x86/kvm/vmx/vmx.h | 5 ++---
3 files changed, 27 insertions(+), 17 deletions(-)
base-commit: 8b9c948fd3c1cbd8fed00646e11651cf3d4c86cc
--
2.35.1.574.g5d30c73bfb-goog
next reply other threads:[~2022-02-24 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 19:19 Sean Christopherson [this message]
2022-02-24 19:19 ` [PATCH 1/2] Revert "KVM: VMX: Save HOST_CR3 in vmx_set_host_fs_gs()" Sean Christopherson
2022-02-24 19:19 ` [PATCH 2/2] Revert "KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()" Sean Christopherson
2022-02-25 2:39 ` Lai Jiangshan
2022-02-25 10:29 [PATCH 0/2] KVM: VMX: Revert back to refreshing HOST_CR3 at ->run 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=20220224191917.3508476-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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®