All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Woods <brian.woods@amd.com>
To: Juergen Gross <jgross@suse.com>
Cc: 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 13:59:16 -0500	[thread overview]
Message-ID: <20180620185915.GA2338@amd.com> (raw)
In-Reply-To: <20180620172020.GA1880@amd.com>

On Wed, Jun 20, 2018 at 12:20:21PM -0500, Brian Woods wrote:
> On Wed, Jun 20, 2018 at 08:34:13AM +0200, Juergen Gross wrote:
> Juergen,
> 
> It works for Dom0.  You see a lot of messages that are like:
> (XEN) emul-priv-op.c:1166:d0v1 Domain attempted WRMSR c0011020 from 0x0206800000000000 to 0x0206800000000400
> (XEN) emul-priv-op.c:1166:d0v0 Domain attempted WRMSR c0011020 from 0x0206800000000000 to 0x0206800000000400
> 
> But it boots up.  I'll test a DomU with a newer kernel after I get back
> from lunch.
> 
> -- 
> Brian Woods

It works on PV and HVM guests.

I'll reply to Andy's email soon.  Have a meeting in 2 minutes...

-- 
Brian Woods

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2018-06-20 18:59 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
2018-06-20 18:59     ` Brian Woods [this message]

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=20180620185915.GA2338@amd.com \
    --to=brian.woods@amd.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.