From: Takahiro Itazuri <itazur@amazon.com>
To: <bp@alien8.de>
Cc: <dave.hansen@linux.intel.com>, <itazur@amazon.com>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<mingo@redhat.com>, <pbonzini@redhat.com>, <seanjc@google.com>,
<tglx@linutronix.de>, <x86@kernel.org>, <zulinx86@gmail.com>
Subject: Re: [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests
Date: Tue, 28 Feb 2023 19:41:53 +0000 [thread overview]
Message-ID: <20230228194153.46995-1-itazur@amazon.com> (raw)
In-Reply-To: <Y/5U3N0XfRaZ2KkX@zn.tnic>
Date: Tue, 28 Feb 2023 20:24:12 +0100
From: Borislav Petkov <bp@alien8.de>
> I'd prefer if VMMs did supply whatever they prefer to the guests
> instead. None of those bits are used in the kernel for mitigations, as
> you've realized.
It is true that the kernel does not use those bits at all, but any
codes could be run inside guests.
One of examples is the following spectre/meltdown checker scipt used as
de facto standard.
https://github.com/speed47/spectre-meltdown-checker/blob/master/spectre-meltdown-checker.sh#L2768
Best regards,
Takahiro Itazuri
next prev parent reply other threads:[~2023-02-28 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 21:05 [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests Takahiro Itazuri
2023-02-27 21:05 ` [PATCH 1/2] x86/cpufeatures: Add AMD-specific IBRS bits Takahiro Itazuri
2023-02-27 21:05 ` [PATCH 2/2] KVM: x86: Propagate AMD-specific IBRS related bits Takahiro Itazuri
2023-02-27 21:40 ` [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests Borislav Petkov
2023-02-28 18:13 ` Takahiro Itazuri
2023-02-28 19:24 ` Borislav Petkov
2023-02-28 19:41 ` Takahiro Itazuri [this message]
2023-02-28 20:45 ` Borislav Petkov
2023-02-28 22:24 ` Takahiro Itazuri
2023-02-28 22:50 ` Borislav Petkov
2023-03-06 21:16 ` Sean Christopherson
2023-03-06 21:25 ` Paolo Bonzini
2023-03-06 21:44 ` Borislav Petkov
2023-03-06 21:47 ` Paolo Bonzini
2023-03-06 21:54 ` Borislav Petkov
2023-03-07 18:49 ` Sean Christopherson
2023-03-07 18:58 ` Borislav Petkov
2023-03-07 19:28 ` Sean Christopherson
2023-03-07 19:55 ` Borislav Petkov
2023-03-06 21:31 ` 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=20230228194153.46995-1-itazur@amazon.com \
--to=itazur@amazon.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zulinx86@gmail.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