From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Chao Gao <chao.gao@intel.com>,
antonio.gomez.iglesias@linux.intel.com,
Daniel Sneddon <daniel.sneddon@linux.intel.com>
Subject: Re: [PATCH] target/i386: Export RFDS bit to guests
Date: Sun, 17 Mar 2024 22:30:10 -0700 [thread overview]
Message-ID: <20240318053010.6rlue36sygewcnvu@desk> (raw)
In-Reply-To: <ZfP9uor+3z9hT+5I@intel.com>
On Fri, Mar 15, 2024 at 03:50:18PM +0800, Zhao Liu wrote:
> > Make RFDS_CLEAR and RFDS_NO bits available to guests.
>
> Are these two bits going to be supported by microcode updates to
> existing products?
RFDS_CLEAR is supported by the microcode update that is needed to
mitigate RFDS. RFDS_NO will be supported by future unaffected parts and
some of the existing parts. AFAIK, not all unaffected existing parts
will get RFDS_NO, for such parts KVM synthesizes RFDS_NO.
> (Let me aslo attach the related spec to make it easy for more people to
> learn about backgrounds:
> https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/advisory-guidance/register-file-data-sampling.html)
>
> > Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> > ---
> > target/i386/cpu.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
>
> LGTM,
>
> Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Thank you.
next prev parent reply other threads:[~2024-03-18 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 14:53 [PATCH] target/i386: Export RFDS bit to guests Pawan Gupta
2024-03-15 7:50 ` Zhao Liu
2024-03-18 5:30 ` Pawan Gupta [this message]
2024-03-19 4:22 ` Xiaoyao Li
2024-03-19 15:08 ` Pawan Gupta
2024-03-20 0:23 ` Xiaoyao Li
2024-03-20 0:26 ` Pawan Gupta
2024-03-20 10:35 ` 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=20240318053010.6rlue36sygewcnvu@desk \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=antonio.gomez.iglesias@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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;
as well as URLs for NNTP newsgroup(s).