From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v2 2/4] x86: split opt_pv_l1tf
Date: Tue, 2 Oct 2018 17:43:45 +0100 [thread overview]
Message-ID: <da96d011-e3ed-b2d4-63a2-505c0617555e@citrix.com> (raw)
In-Reply-To: <5BB20E8D02000078001ED368@prv1-mh.provo.novell.com>
On 01/10/18 13:09, Jan Beulich wrote:
> Use separate tracking variables for the hardware domain and DomU-s.
>
> No functional change intended, but adjust the comment in
> init_speculation_mitigations() to match prior as well as resulting code.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>, but with one
suggested deletion.
> @@ -889,18 +892,16 @@ void __init init_speculation_mitigations
>
> /*
> * By default, enable PV domU L1TF mitigations on all L1TF-vulnerable
> - * hardware, except when running in shim mode.
> + * hardware, except when running in shim mode, and - at least for the
> + * time being - also excepting the hardware domain.
I'm not sure this addition is helpful. We already state PV domU above.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-10-02 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 12:02 [PATCH v2 0/4] x86: fix "xpti=" and "pv-l1tf=" yet again Jan Beulich
2018-10-01 12:09 ` [PATCH v2 1/4] x86: split opt_xpti Jan Beulich
2018-10-02 16:36 ` Andrew Cooper
2018-10-01 12:09 ` [PATCH v2 2/4] x86: split opt_pv_l1tf Jan Beulich
2018-10-02 16:43 ` Andrew Cooper [this message]
2018-10-04 10:03 ` Jan Beulich
2018-10-01 12:10 ` [PATCH v2 3/4] x86: fix "xpti=" and "pv-l1tf=" yet again Jan Beulich
2018-10-02 16:58 ` Andrew Cooper
2018-10-01 12:11 ` [PATCH v2 4/4] x86: support "pv-l1tf=default" Jan Beulich
2018-10-02 16:59 ` Andrew Cooper
2018-10-04 10:09 ` Jan Beulich
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=da96d011-e3ed-b2d4-63a2-505c0617555e@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.