From: Arjan van de Ven <arjan@linux.intel.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: jmattson@google.com, dwmw@amazon.co.uk, bp@alien8.de,
thomas.lendacky@amd.com, aliguori@amazon.com,
pbonzini@redhat.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 6/7] x86/svm: Set IBPB when running a different VCPU
Date: Tue, 9 Jan 2018 07:56:52 -0800 [thread overview]
Message-ID: <d7c9f133-97a8-db07-0c56-36b8ae2fba3a@linux.intel.com> (raw)
In-Reply-To: <2779f941-9011-4dd1-8ef0-6b035fbf0e2f@default>
>> I'm sorry I'm not familiar with your L0/L1/L2 terminology
>> (maybe it's before coffee has had time to permeate the brain)
>
> These are standard terminology for guest levels:
> L0 == hypervisor that runs on bare-metal
> L1 == hypervisor that runs as L0 guest.
> L2 == software that runs as L1 guest.
> (We are talking about nested virtualization here)
1. I really really hope that the guests don't use IBRS but use retpoline. At least for Linux that is going to be the prefered approach.
2. For the CPU, there really is only "bare metal" vs "guest"; all guests are "guests" no matter how deeply nested. So for the language of privilege domains etc,
nested guests equal their parent.
next prev parent reply other threads:[~2018-01-09 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:33 [PATCH 6/7] x86/svm: Set IBPB when running a different VCPU Liran Alon
2018-01-09 15:56 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 16:01 Liran Alon
2018-01-09 15:00 Liran Alon
2018-01-09 15:19 ` Arjan van de Ven
2018-01-09 16:17 ` Paolo Bonzini
2018-01-09 16:23 ` Arjan van de Ven
2018-01-09 16:49 ` Paolo Bonzini
2018-01-09 20:39 ` Konrad Rzeszutek Wilk
2018-01-09 20:47 ` Konrad Rzeszutek Wilk
2018-01-09 20:57 ` Jim Mattson
2018-01-09 21:11 ` Konrad Rzeszutek Wilk
2018-01-09 21:19 ` Jim Mattson
2018-01-09 21:42 ` Paolo Bonzini
2018-01-09 21:59 ` Jim Mattson
2018-01-09 21:56 ` Paolo Bonzini
2018-01-09 11:31 Liran Alon
2018-01-09 11:41 ` Paolo Bonzini
2018-01-09 14:30 ` Arjan van de Ven
2018-01-08 18:08 [PATCH 0/7] KVM: x86: expose CVE-2017-5715 ("Spectre variant 2") mitigations to guest Paolo Bonzini
2018-01-08 18:08 ` [PATCH 6/7] x86/svm: Set IBPB when running a different VCPU Paolo Bonzini
2018-01-08 20:00 ` Liran Alon
2018-01-09 11:07 ` 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=d7c9f133-97a8-db07-0c56-36b8ae2fba3a@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=aliguori@amazon.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.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