From: David Vrabel <david.vrabel@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
<boris.ostrovsky@oracle.com>, <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [V1 PATCH 0/2] Linux PVH: set EFER bits..
Date: Thu, 28 Aug 2014 15:08:24 +0100 [thread overview]
Message-ID: <53FF37D8.8070509@citrix.com> (raw)
In-Reply-To: <1409178815-2026-1-git-send-email-mukesh.rathor@oracle.com>
On 27/08/14 23:33, Mukesh Rathor wrote:
> Resending with comments fixed up. Please note, these are no longer
> AMD only, but address existing broken boot and broken NX on intel.
It's no secret that I'm fed up with the cavalier attitude to the PVH ABI.
The Xen change that broke Linux PVH guests must be reverted. This
change may also have broken other guests (e.g., Mirage or one of the
other unikernel OSes).
The documented posted by Roger is a good start, but I'm still not going
to apply any PVH patches to Linux until the ABI is agreed and stable and
the document is committed to the Xen repo.
David
next prev parent reply other threads:[~2014-08-28 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 22:33 [V1 PATCH 0/2] Linux PVH: set EFER bits Mukesh Rathor
2014-08-27 22:33 ` [V1 PATCH 1/2] PVH: set EFER.NX and EFER.SCE for boot vcpu Mukesh Rathor
2014-08-28 14:18 ` [Xen-devel] " David Vrabel
2014-08-28 23:59 ` Mukesh Rathor
2014-08-27 22:33 ` [V1 PATCH 2/2] PVH: set EFER.NX and EFER.SCE for secondary vcpus Mukesh Rathor
2014-08-28 14:24 ` [Xen-devel] " David Vrabel
2014-08-28 14:08 ` David Vrabel [this message]
2014-08-28 14:15 ` [Xen-devel] [V1 PATCH 0/2] Linux PVH: set EFER bits 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=53FF37D8.8070509@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.rathor@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox