From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sandipan Das <sandipan.das@amd.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
Jing Liu <jing2.liu@intel.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Wyes Karny <wyes.karny@amd.com>, Borislav Petkov <bp@alien8.de>,
Babu Moger <babu.moger@amd.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Jim Mattson <jmattson@google.com>,
x86@kernel.org
Subject: Re: [PATCH 04/13] KVM: nSVM: clean up copying of int_ctl fields back to vmcb01/vmcb12
Date: Thu, 17 Nov 2022 20:15:32 +0000 [thread overview]
Message-ID: <Y3aWZJo8M2li/7BB@google.com> (raw)
In-Reply-To: <20221117143242.102721-5-mlevitsk@redhat.com>
On Thu, Nov 17, 2022, Maxim Levitsky wrote:
> Clean up the nested_sync_int_ctl_from_vmcb02:
>
> 1. The comment about preservation of V_IRQ is wrong: when the L2 doesn't
> use virtual interrupt masking, then the field just doesn't exist in
> vmcb12 thus it should not be touched at all.
> Since it is unused in this case, touching it doesn't matter that much,
> so the bug is theoretical.
>
> 2. When the L2 doesn't use virtual interrupt masking, then in the *theory*
> if KVM uses the feature, it should copy the changes to V_IRQ* bits from
> vmcb02 to vmcb01.
>
> In practise, KVM only uses it for detection of the interrupt window,
> and it happens to re-open it on each nested VM exit because
> kvm_set_rflags happens to raise the KVM_REQ_EVENT.
> Do this explicitly.
>
> 3. Add comment on why we don't need to copy V_GIF from vmcb02 to vmcb01
> when nested guest doesn't use nested V_GIF (and thus L1's GIF is in
> vmcb02 while nested), even though it can in theory affect L1's GIF.
>
> 4. Add support code to also copy some bits of int_ctl from
> vmcb02 to vmcb01.
> Currently there are none.
Unless it's impossible for whatever reason, this patch should be split into
multiple patches. IIUC, there are at least 2 different functional changes being
made, they just happen to not have any actual impact on things.
> No (visible) functional change is intended.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> ---
> arch/x86/kvm/svm/nested.c | 47 ++++++++++++++++++++++++++-------------
> 1 file changed, 32 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> index 54eb152e2b60b6..1f2b8492c8782f 100644
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -410,28 +410,45 @@ void nested_copy_vmcb_save_to_cache(struct vcpu_svm *svm,
> static void nested_sync_int_ctl_from_vmcb02(struct vcpu_svm *svm,
> struct vmcb *vmcb12)
> {
> - u32 mask;
> + struct vmcb *vmcb02 = svm->nested.vmcb02.ptr;
> + struct vmcb *vmcb01 = svm->vmcb01.ptr;
> +
> + /* bitmask of bits of int_ctl that we copy from vmcb02 to vmcb12*/
> + u32 l2_to_l1_mask = 0;
> + /* bitmask of bits of int_ctl that we copy from vmcb02 to vmcb01*/
> + u32 l2_to_l0_mask = 0;
>
> - /* Only a few fields of int_ctl are written by the processor. */
Can this comment be kept in some form? I found it super useful when reading this
code just now.
> - mask = V_IRQ_MASK | V_TPR_MASK;
> - if (!(svm->nested.ctl.int_ctl & V_INTR_MASKING_MASK) &&
> - svm_is_intercept(svm, INTERCEPT_VINTR)) {
> + if (svm->nested.ctl.int_ctl & V_INTR_MASKING_MASK)
> + l2_to_l1_mask |= V_IRQ_MASK | V_TPR_MASK;
> + else {
> /*
> - * In order to request an interrupt window, L0 is usurping
> - * svm->vmcb->control.int_ctl and possibly setting V_IRQ
> - * even if it was clear in L1's VMCB. Restoring it would be
> - * wrong. However, in this case V_IRQ will remain true until
> - * interrupt_window_interception calls svm_clear_vintr and
> - * restores int_ctl. We can just leave it aside.
> + * If IRQ window was opened while in L2, it must be reopened
> + * after the VM exit
> + *
> + * vTPR value doesn't need to be copied from vmcb02 to vmcb01
> + * because it is synced from/to apic registers on each VM exit
> */
> - mask &= ~V_IRQ_MASK;
> + if (vmcb02->control.int_ctl & V_IRQ_MASK)
> + kvm_make_request(KVM_REQ_EVENT, &svm->vcpu);
> }
>
> if (nested_vgif_enabled(svm))
> - mask |= V_GIF_MASK;
> + l2_to_l1_mask |= V_GIF_MASK;
> + else
> + /* There is no need to sync V_GIF from vmcb02 to vmcb01
> + * because GIF is cleared on VMexit, thus even though
> + * nested guest can control host's GIF, on VM exit
> + * its set value is lost
> + */
> + ;
The "else ... ;" is unnecessary, just throw the block comment above the nested
vGIF if-statment, e.g. if I'm understanding everything, this?
/*
* If nested vGIF is not enabled, L2 has access to L1's "real" GIF. In
* this case, there's no need to sync V_GIF from vmcb02 to vmcb01
* because GIF is cleared on VM-Exit, thus any changes made by L2 are
* overwritten on VM-Exit to L1.
*/
if (nested_vgif_enabled(svm))
l2_to_l1_mask |= V_GIF_MASK;
> +
> + vmcb12->control.int_ctl =
> + (svm->nested.ctl.int_ctl & ~l2_to_l1_mask) |
> + (vmcb02->control.int_ctl & l2_to_l1_mask);
>
> - vmcb12->control.int_ctl &= ~mask;
> - vmcb12->control.int_ctl |= svm->vmcb->control.int_ctl & mask;
> + vmcb01->control.int_ctl =
> + (vmcb01->control.int_ctl & ~l2_to_l0_mask) |
> + (vmcb02->control.int_ctl & l2_to_l0_mask);
No need for wrapping immediately after the "=", these all fit under the soft limit:
vmcb12->control.int_ctl = (svm->nested.ctl.int_ctl & ~l2_to_l1_mask) |
(vmcb02->control.int_ctl & l2_to_l1_mask);
vmcb01->control.int_ctl = (vmcb01->control.int_ctl & ~l2_to_l0_mask) |
(vmcb02->control.int_ctl & l2_to_l0_mask);
next prev parent reply other threads:[~2022-11-17 20:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 14:32 [PATCH 00/13] SVM: vNMI (with my fixes) Maxim Levitsky
2022-11-17 14:32 ` [PATCH 01/13] KVM: nSVM: don't sync back tlb_ctl on nested VM exit Maxim Levitsky
2022-11-17 14:32 ` [PATCH 02/13] KVM: nSVM: don't call nested_sync_control_from_vmcb02 on each " Maxim Levitsky
2022-11-17 20:04 ` Sean Christopherson
2022-11-21 11:07 ` Maxim Levitsky
2022-11-21 17:51 ` Sean Christopherson
2022-11-17 14:32 ` [PATCH 03/13] KVM: nSVM: rename nested_sync_control_from_vmcb02 to nested_sync_int_ctl_from_vmcb02 Maxim Levitsky
2022-11-17 14:32 ` [PATCH 04/13] KVM: nSVM: clean up copying of int_ctl fields back to vmcb01/vmcb12 Maxim Levitsky
2022-11-17 20:15 ` Sean Christopherson [this message]
2022-11-21 11:10 ` Maxim Levitsky
2022-11-17 14:32 ` [PATCH 05/13] x86/cpu: Add CPUID feature bit for VNMI Maxim Levitsky
2022-11-17 14:32 ` [PATCH 06/13] KVM: SVM: Add VNMI bit definition Maxim Levitsky
2022-11-17 14:37 ` Borislav Petkov
2022-11-17 16:42 ` Sean Christopherson
2022-11-17 17:07 ` Borislav Petkov
2022-11-17 20:33 ` Sean Christopherson
2022-11-17 20:27 ` Sean Christopherson
2022-11-17 14:32 ` [PATCH 07/13] KVM: SVM: Add VNMI support in get/set_nmi_mask Maxim Levitsky
2022-11-17 18:54 ` Sean Christopherson
2022-11-21 12:36 ` Maxim Levitsky
2022-11-21 17:18 ` Sean Christopherson
2022-12-04 18:42 ` Maxim Levitsky
2022-12-06 18:27 ` Sean Christopherson
2022-11-17 14:32 ` [PATCH 08/13] KVM: SVM: Report NMI not allowed when Guest busy handling VNMI Maxim Levitsky
2022-11-17 14:32 ` [PATCH 09/13] KVM: SVM: allow NMI window with vNMI Maxim Levitsky
2022-11-17 18:21 ` Sean Christopherson
2022-11-21 13:40 ` Maxim Levitsky
2022-11-17 14:32 ` [PATCH 10/13] KVM: SVM: Add VNMI support in inject_nmi Maxim Levitsky
2022-11-21 17:12 ` Sean Christopherson
2022-11-17 14:32 ` [PATCH 11/13] KVM: nSVM: implement nested VNMI Maxim Levitsky
2022-11-17 14:32 ` [PATCH 12/13] KVM: nSVM: emulate VMEXIT_INVALID case for " Maxim Levitsky
2022-11-17 20:18 ` Sean Christopherson
2022-11-17 14:32 ` [PATCH 13/13] KVM: SVM: Enable VNMI feature Maxim Levitsky
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=Y3aWZJo8M2li/7BB@google.com \
--to=seanjc@google.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=jpoimboe@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=tglx@linutronix.de \
--cc=wyes.karny@amd.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).