From: Paolo Bonzini <pbonzini@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, berrange@redhat.com,
Eduardo Habkost <ehabkost@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v3 2/2] qemu-cpu-models.rst: Document -noTSX, mds-no, taa-no, and tsx-ctrl
Date: Thu, 20 Feb 2020 15:52:48 +0100 [thread overview]
Message-ID: <4c3f3d85-9499-2e48-124b-18cc0dc36c8a@redhat.com> (raw)
In-Reply-To: <20200220142001.20774-3-kchamart@redhat.com>
Two small changes...
On 20/02/20 15:20, Kashyap Chamarthy wrote:
> + Recommended to inform the guest that it can disable the Intel TSX
> + (Transactional Synchronization Extensions) feature; or, if the
> + processor is vulnerable, use the Intel VERW instruction (a
> + processor-level instruction that performs checks on memory access) as
> + a mitigation for the TAA vulnerability. (For details, refer to this
> + `Intel's deep-dive into
> + MDS <https://software.intel.com/security-software-guidance/insights/deep-dive-intel-analysis-microarchitectural-data-sampling>`_.)
... refer to Intel's `deep dive into MDS <...>`_.
(I don't know what the trailing underscore is for. I reaffirm my
definition of rST as the Perl of markup formats).
> +
> + Expose this to the guest OS if and only if: (a) the host has TSX
> + enabled; *and* (b) the guest has ``rtm`` CPU flag enabled.
> +
> + By disabling TSX, KVM-based guests can avoid paying the price of
> + mitigting TSX-based attacks.
"mitigating"
Paolo
next prev parent reply other threads:[~2020-02-20 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:19 [PATCH v3 0/2] qemu-cpu-models: Convert to rST; document other MSR bits Kashyap Chamarthy
2020-02-20 14:20 ` [PATCH v3 1/2] docs: Convert qemu-cpu-models.texi to rST Kashyap Chamarthy
2020-02-21 15:16 ` Peter Maydell
2020-02-21 15:31 ` Daniel P. Berrangé
2020-02-21 15:36 ` Peter Maydell
2020-02-25 9:16 ` Kashyap Chamarthy
2020-02-25 14:22 ` Kashyap Chamarthy
2020-02-20 14:20 ` [PATCH v3 2/2] qemu-cpu-models.rst: Document -noTSX, mds-no, taa-no, and tsx-ctrl Kashyap Chamarthy
2020-02-20 14:52 ` Paolo Bonzini [this message]
2020-02-20 15:45 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 14:02 [PATCH v3 0/2] qemu-cpu-models: Convert to rST; document other MSR bits Kashyap Chamarthy
2020-02-20 14:02 ` [PATCH v3 2/2] qemu-cpu-models.rst: Document -noTSX, mds-no, taa-no, and tsx-ctrl Kashyap Chamarthy
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=4c3f3d85-9499-2e48-124b-18cc0dc36c8a@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kchamart@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).