From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.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: Wed, 20 Mar 2024 08:23:39 +0800 [thread overview]
Message-ID: <1f06acaf-c63e-42b3-b355-3024ded1fd8e@intel.com> (raw)
In-Reply-To: <20240319150851.kllaqhbfysfkqcey@desk>
On 3/19/2024 11:08 PM, Pawan Gupta wrote:
> On Tue, Mar 19, 2024 at 12:22:08PM +0800, Xiaoyao Li wrote:
>> On 3/13/2024 10:53 PM, Pawan Gupta wrote:
>>> Register File Data Sampling (RFDS) is a CPU side-channel vulnerability
>>> that may expose stale register value. CPUs that set RFDS_NO bit in MSR
>>> IA32_ARCH_CAPABILITIES indicate that they are not vulnerable to RFDS.
>>> Similarly, RFDS_CLEAR indicates that CPU is affected by RFDS, and has
>>> the microcode to help mitigate RFDS.
>>>
>>> Make RFDS_CLEAR and RFDS_NO bits available to guests.
>>
>> What's the status of KVM part?
>
> KVM part is already upstreamed and backported:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.8.1&id=50d33b98b1e23d1cd8743b3cac7a0ae5718b8b00
I see. It was not sent to kvm maillist and not merged through KVM tree.
With KVM part in palce,
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
next prev parent reply other threads:[~2024-03-20 0:24 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
2024-03-19 4:22 ` Xiaoyao Li
2024-03-19 15:08 ` Pawan Gupta
2024-03-20 0:23 ` Xiaoyao Li [this message]
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=1f06acaf-c63e-42b3-b355-3024ded1fd8e@intel.com \
--to=xiaoyao.li@intel.com \
--cc=antonio.gomez.iglesias@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=pawan.kumar.gupta@linux.intel.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).