From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Lars Kurth <lars.kurth@citrix.com>, Tim Deegan <tim@xen.org>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: RFC: making the PVH 64bit ABI as stableo
Date: Fri, 05 Jun 2015 12:43:41 -0400 [thread overview]
Message-ID: <5571D1BD.1090108@oracle.com> (raw)
In-Reply-To: <5571CB4D.5010403@citrix.com>
On 06/05/2015 12:16 PM, Roger Pau Monné wrote:
> El 03/06/15 a les 14.08, Jan Beulich ha escrit:
>>>>> On 03.06.15 at 12:02, <stefano.stabellini@eu.citrix.com> wrote:
>>> On Tue, 2 Jun 2015, Andrew Cooper wrote:
>>>> With my x86 maintainer hat on, the following is an absolute minimum set
>>>> of prerequisite for PVH.
>>>>
>>>> * 32bit support
>>> Could you please explain why 32bit is important to get PVH out of tech
>>> preview? I don't see 32 bit OSes as an important use case. Maybe there
>>> is more behind it that I cannot see.
>> The primary reason was named before: 32-bit support will likely
>> end up changing the way 64-bit guests get launched.
> I can work on the new boot ABI, even if it's just a design document now,
> but the actual implementation needs to be done on top of the 32-bit
> support series.
>
> Boris, do you think you could send an early RFC of your 32-bit support
> series in a couple of weeks at most?
That's highly unlikely. For one, I am still unable to boot MP guests. In
addition, it is all held together by rubber bands and matchsticks so
calling it an RFC would be an insult to RFCs. (for example, I apparently
broke HVM somewhere along the way).
-boris
next prev parent reply other threads:[~2015-06-05 16:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 15:11 RFC: making the PVH 64bit ABI as stable Roger Pau Monné
2015-06-02 15:37 ` 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 [this message]
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=5571D1BD.1090108@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.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.