From: Brian Woods <brian.woods@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Woods <brian.woods@amd.com>,
xen-devel@lists.xen.org
Subject: Re: Dom0 Failing to Boot with Recent Linux Kernels (Spectre Mitigations)
Date: Wed, 20 Jun 2018 17:41:08 -0500 [thread overview]
Message-ID: <20180620224105.GC2338@amd.com> (raw)
In-Reply-To: <71b5705f-961e-88f8-8163-41b0e51b3706@citrix.com>
On Thu, Jun 21, 2018 at 01:55:54AM +0800, Andrew Cooper wrote:
> That is Linux trying to enable the SSBD via the native mechanism (on
> Fam17h hardware I'm guessing, give the bit position).
>
> Like many of the other mitigations, a PV guest knows it is virtualised
> and shouldn’t be playing with this MSR.
>
> OTOH, Xen should be implementing the AMD SSBD spec and allowing for
> virtualised control of SSBD. Sadly, I was only show the whitepaper with
> insufficient time before the SSBD embargo to implement it in XSA-263,
> and haven't had time since.
>
> ~Andrew
I'll take a look into updating it for AMD related processors then. I
will talk with some people internally who did the work for Linux and
see what needs to be done etc.
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-20 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 21:30 Dom0 Failing to Boot with Recent Linux Kernels (Spectre Mitigations) Brian Woods
2018-06-20 3:31 ` Boris Ostrovsky
2018-06-20 6:17 ` Juergen Gross
2018-06-20 14:27 ` Boris Ostrovsky
2018-06-20 14:52 ` Boris Ostrovsky
2018-06-20 6:34 ` Juergen Gross
2018-06-20 17:20 ` Brian Woods
2018-06-20 17:55 ` Andrew Cooper
2018-06-20 22:41 ` Brian Woods [this message]
2018-06-20 18:59 ` Brian Woods
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=20180620224105.GC2338@amd.com \
--to=brian.woods@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xen.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.