From: Zhao Liu <zhao1.liu@intel.com>
To: Tao Su <tao1.su@linux.intel.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, imammedo@redhat.com,
xiaoyao.li@intel.com, zhao1.liu@linux.intel.com,
xuelian.guo@intel.com
Subject: Re: [PATCH 2/4] target/i386: Export BHI_NO bit to guests
Date: Tue, 21 Jan 2025 20:41:17 +0800 [thread overview]
Message-ID: <Z4+V7e8KObBRCctM@intel.com> (raw)
In-Reply-To: <20250121020650.1899618-3-tao1.su@linux.intel.com>
On Tue, Jan 21, 2025 at 10:06:48AM +0800, Tao Su wrote:
> Date: Tue, 21 Jan 2025 10:06:48 +0800
> From: Tao Su <tao1.su@linux.intel.com>
> Subject: [PATCH 2/4] target/i386: Export BHI_NO bit to guests
> X-Mailer: git-send-email 2.34.1
>
> Branch History Injection (BHI) is a CPU side-channel vulnerability, where
> an attacker may manipulate branch history before transitioning from user
> to supervisor mode or from VMX non-root/guest to root mode. CPUs that set
> BHI_NO bit in MSR IA32_ARCH_CAPABILITIES to indicate no additional
> mitigation is required to prevent BHI.
>
> Make BHI_NO bit available to guests.
>
> Tested-by: Xuelian Guo <xuelian.guo@intel.com>
> Signed-off-by: Tao Su <tao1.su@linux.intel.com>
> ---
> target/i386/cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
next prev parent reply other threads:[~2025-01-21 12:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 2:06 [PATCH 0/4] Introduce SierraForest-v2 and ClearwaterForest CPU model Tao Su
2025-01-21 2:06 ` [PATCH 1/4] target/i386: Introduce SierraForest-v2 model Tao Su
2025-01-21 12:40 ` Zhao Liu
2025-01-21 17:34 ` Pawan Gupta
2025-01-22 1:16 ` Tao Su
2025-01-22 4:32 ` Pawan Gupta
2025-01-22 1:44 ` Xiaoyao Li
2025-01-21 2:06 ` [PATCH 2/4] target/i386: Export BHI_NO bit to guests Tao Su
2025-01-21 12:41 ` Zhao Liu [this message]
2025-01-21 17:38 ` Pawan Gupta
2025-01-22 1:44 ` Xiaoyao Li
2025-01-21 2:06 ` [PATCH 3/4] target/i386: Add new CPU model ClearwaterForest Tao Su
2025-01-21 13:20 ` Zhao Liu
2025-01-22 1:44 ` Xiaoyao Li
2025-01-21 2:06 ` [PATCH 4/4] docs: Add GNR, SRF and CWF CPU models Tao Su
2025-01-21 3:12 ` BALATON Zoltan
2025-01-21 3:18 ` Tao Su
2025-01-21 13:31 ` Zhao Liu
2025-01-22 1:21 ` Tao Su
2025-01-21 13:38 ` [PATCH 0/4] Introduce SierraForest-v2 and ClearwaterForest CPU model Paolo Bonzini
2025-01-22 1:21 ` Tao Su
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=Z4+V7e8KObBRCctM@intel.com \
--to=zhao1.liu@intel.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tao1.su@linux.intel.com \
--cc=xiaoyao.li@intel.com \
--cc=xuelian.guo@intel.com \
--cc=zhao1.liu@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.