From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
jpoimboe@kernel.org, Babu Moger <babu.moger@amd.com>,
Dario Faggioli <dfaggioli@suse.com>, Fabian Vogt <fvogt@suse.de>,
Nikolay Borisov <nik.borisov@suse.com>
Subject: Re: [PATCH] target/i386: Expose IBPB-BRTYPE and SBPB CPUID bits to the guest
Date: Wed, 04 Sep 2024 09:47:06 -0300 [thread overview]
Message-ID: <8734mfmvqt.fsf@suse.de> (raw)
In-Reply-To: <20240805202041.5936-1-farosas@suse.de>
Fabiano Rosas <farosas@suse.de> writes:
> According to AMD's Speculative Return Stack Overflow whitepaper (link
> below), the hypervisor should synthesize the value of IBPB_BRTYPE and
> SBPB CPUID bits to the guest.
>
> Support for this is already present in the kernel with commit
> e47d86083c66 ("KVM: x86: Add SBPB support") and commit 6f0f23ef76be
> ("KVM: x86: Add IBPB_BRTYPE support").
>
> Add support in QEMU to expose the bits to the guest OS.
>
> host:
> # cat /sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow
> Mitigation: Safe RET
>
> before (guest):
> $ cpuid -l 0x80000021 -1 -r
> 0x80000021 0x00: eax=0x00000045 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
> ^
> $ cat /sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow
> Vulnerable: Safe RET, no microcode
>
> after (guest):
> $ cpuid -l 0x80000021 -1 -r
> 0x80000021 0x00: eax=0x18000045 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
> ^
> $ cat /sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow
> Mitigation: Safe RET
>
> Reported-by: Fabian Vogt <fvogt@suse.de>
> Link: https://www.amd.com/content/dam/amd/en/documents/corporate/cr/speculative-return-stack-overflow-whitepaper.pdf
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
> ---
> More info on this thread:
> https://lore.kernel.org/r/68f8b8b1ca1bf58b059f52afbd1c9c51108a074a.camel@suse.com
> ---
> target/i386/cpu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 85ef7452c0..d33401c922 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -1221,8 +1221,8 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
> NULL, NULL, NULL, NULL,
> NULL, NULL, NULL, NULL,
> NULL, NULL, NULL, NULL,
> - NULL, NULL, NULL, NULL,
> - NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, "sbpb",
> + "ibpb-brtype", NULL, NULL, NULL,
> },
> .cpuid = { .eax = 0x80000021, .reg = R_EAX, },
> .tcg_features = 0,
Ping, any thoughts on this one?
next prev parent reply other threads:[~2024-09-04 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 20:20 [PATCH] target/i386: Expose IBPB-BRTYPE and SBPB CPUID bits to the guest Fabiano Rosas
2024-09-04 12:47 ` Fabiano Rosas [this message]
2024-09-04 12:53 ` 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=8734mfmvqt.fsf@suse.de \
--to=farosas@suse.de \
--cc=babu.moger@amd.com \
--cc=dfaggioli@suse.com \
--cc=fvogt@suse.de \
--cc=jpoimboe@kernel.org \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).