From: "Roger Pau Monné" <roger.pau@citrix.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: RFC: making the PVH 64bit ABI as stable
Date: Tue, 2 Jun 2015 17:11:21 +0200 [thread overview]
Message-ID: <556DC799.5040300@citrix.com> (raw)
Hello,
The document describing the PVH interface was committed 9 months ago
[1], and since then there hasn't been any change regarding the
interface. PVH is still missing features in order to have feature parity
with pure PV, mainly:
- DomU miration support.
- PCI passthrough support.
- 32bit support.
- AMD support.
AFAICT however none of these features are going to change the current
ABI. PCI passthrough might expand it, by adding new hypercalls, but I
don't think this should prevent us from marking the current ABI as
stable. ARM for example doesn't have PCI passthrough yet or migration
support, but the ABI has been marked as stable.
To that end, I would like to request the 64bit PVH ABI to be marked as
stable for DomUs. This is needed so external projects (like PVH support
for grub2) can progress.
Roger.
[1]
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=a9be04f504bafd9b30094d7c825ed43933b028af
next reply other threads:[~2015-06-02 15:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 15:11 Roger Pau Monné [this message]
2015-06-02 15:37 ` RFC: making the PVH 64bit ABI as stable Andrew Cooper
2015-06-02 15:44 ` Jan Beulich
2015-06-02 16:51 ` RFC: making the PVH 64bit ABI as stableo Stefano Stabellini
2015-06-02 17:09 ` Andrew Cooper
2015-06-03 9:00 ` Ian Campbell
2015-06-03 9:06 ` Andrew Cooper
2015-06-03 9:20 ` Ian Campbell
2015-06-03 10:02 ` Stefano Stabellini
2015-06-03 12:08 ` Jan Beulich
2015-06-03 13:11 ` Stefano Stabellini
2015-06-03 14:59 ` Boris Ostrovsky
2015-06-05 16:16 ` Roger Pau Monné
2015-06-05 16:21 ` Stefano Stabellini
2015-06-05 16:46 ` Boris Ostrovsky
2015-06-05 16:43 ` Boris Ostrovsky
2015-06-05 16:57 ` Andrew Cooper
2015-06-05 17:16 ` Stefano Stabellini
2015-06-05 17:20 ` Boris Ostrovsky
2015-06-05 17:21 ` Andrew Cooper
2015-06-05 21:52 ` Tim Deegan
2015-06-06 9:57 ` Roger Pau Monné
2015-06-06 14:41 ` Andrew Cooper
2015-06-06 15:50 ` Boris Ostrovsky
2015-06-08 14:26 ` Konrad Rzeszutek Wilk
2015-06-08 9:07 ` Ian Campbell
2015-06-02 17:12 ` Boris Ostrovsky
2015-06-03 6:09 ` Jan Beulich
2015-06-03 13:25 ` Boris Ostrovsky
2015-06-03 9:03 ` Ian Campbell
2015-06-03 13:35 ` Boris Ostrovsky
2015-06-05 16:29 ` Ian Campbell
2015-06-10 20:11 ` Elena Ufimtseva
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=556DC799.5040300@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=tim@xen.org \
--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.