From: Chao Gao <chao.gao@intel.com>
To: Jim Mattson <jmattson@google.com>, <pawan.kumar.gupta@intel.com>,
<chen.zhang@intel.com>
Cc: kvm list <kvm@vger.kernel.org>
Subject: Re: BHB-clearing on VM-exit
Date: Wed, 31 Aug 2022 16:22:03 +0800 [thread overview]
Message-ID: <Yw8aK9O2C+38ShCC@gao-cwp> (raw)
In-Reply-To: <CALMp9eRp-cH6=trNby3EY6+ynD6F-AWiThBHiSF8_sgL2UWnkA@mail.gmail.com>
On Tue, Aug 30, 2022 at 04:42:19PM -0700, Jim Mattson wrote:
>Don't we need a software BHB-clearing sequence on VM-exit for Intel
>parts that don't report IA32_ARCH_CAPABILITIES.BHI_NO? What am I
>missing?
I think we need the software mitigation on parts that don't support/enable
BHI_DIS_S of IA32_SPEC_CTRL MSR and don't enumerate BHI_NO.
Pawan, any idea?
>
>https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/branch-history-injection.html
next prev parent reply other threads:[~2022-08-31 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 23:42 BHB-clearing on VM-exit Jim Mattson
2022-08-31 8:22 ` Chao Gao [this message]
2022-09-01 17:46 ` Pawan Gupta
2022-09-01 18:35 ` Jim Mattson
2022-09-02 19:14 ` Pawan Gupta
2022-09-02 19:35 ` Jim Mattson
2022-09-03 2:08 ` Pawan Gupta
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=Yw8aK9O2C+38ShCC@gao-cwp \
--to=chao.gao@intel.com \
--cc=chen.zhang@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pawan.kumar.gupta@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.