From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] nSVM: use svm->nested.save to load vmcb12 registers and avoid TOC/TOU races
Date: Tue, 14 Sep 2021 10:20:32 +0200 [thread overview]
Message-ID: <73b5a5bb-48f2-3a08-c76b-a82b5b69c406@redhat.com> (raw)
In-Reply-To: <21d2bf8c4e3eb3fc5d297fd13300557ec686b625.camel@redhat.com>
On 12/09/2021 12:42, Maxim Levitsky wrote:
>>
>> - if (!nested_vmcb_valid_sregs(vcpu, &vmcb12->save) ||
>> + if (!nested_vmcb_valid_sregs(vcpu, &svm->nested.save) ||
>> !nested_vmcb_check_controls(vcpu, &svm->nested.ctl)) {
> If you use a different struct for the copied fields, then it makes
> sense IMHO to drop the 'control' parameter from nested_vmcb_check_controls,
> and just use the svm->nested.save there directly.
>
Ok, what you say in patch 2 makes sense to me. I can create a new struct
vmcb_save_area_cached, but I need to keep nested.ctl because 1) it is
used also elsewhere, and different fields from the one checked here are
read/set and 2) using another structure (or the same
vmcb_save_area_cached) in its place would just duplicate the same fields
of nested.ctl, creating even more confusion and possible inconsistency.
Let me know if you disagree.
Thank you,
Emanuele
next prev parent reply other threads:[~2021-09-14 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:20 [RFC PATCH 0/3] KVM: nSVM: avoid TOC/TOU race when checking vmcb12 Emanuele Giuseppe Esposito
2021-09-03 10:20 ` [RFC PATCH 1/3] KVM: nSVM: move nested_vmcb_check_cr3_cr4 logic in nested_vmcb_valid_sregs Emanuele Giuseppe Esposito
2021-09-12 10:36 ` Maxim Levitsky
2021-09-03 10:20 ` [RFC PATCH 2/3] nSVM: introduce smv->nested.save to cache save area fields Emanuele Giuseppe Esposito
2021-09-12 10:39 ` Maxim Levitsky
2021-09-28 16:20 ` Paolo Bonzini
2021-09-28 22:23 ` Sean Christopherson
2021-09-29 11:13 ` Paolo Bonzini
2021-09-03 10:20 ` [RFC PATCH 3/3] nSVM: use svm->nested.save to load vmcb12 registers and avoid TOC/TOU races Emanuele Giuseppe Esposito
2021-09-12 10:42 ` Maxim Levitsky
2021-09-14 8:20 ` Emanuele Giuseppe Esposito [this message]
2021-09-14 9:02 ` Maxim Levitsky
2021-09-14 9:12 ` Maxim Levitsky
2021-09-14 9:24 ` Emanuele Giuseppe Esposito
2021-09-14 9:34 ` Maxim Levitsky
2021-09-14 10:52 ` Emanuele Giuseppe Esposito
2021-09-14 11:39 ` Maxim Levitsky
2021-09-28 16:21 ` 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=73b5a5bb-48f2-3a08-c76b-a82b5b69c406@redhat.com \
--to=eesposit@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
all inboxes | Powered by JetHome®