From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <stefano@stabellini.net>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.3 Planning: Taking stock
Date: Wed, 23 Jan 2013 17:10:30 +0000 [thread overview]
Message-ID: <51001986.7020301@eu.citrix.com> (raw)
In-Reply-To: <5100253A02000078000B8D0A@nat28.tlf.novell.com>
On 23/01/13 17:00, Jan Beulich wrote:
>>>> On 23.01.13 at 17:52, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>>> * Xen EFI feature: dom0 able to make use of EFI run-time services
>>>
>> Daniel Kiper is already working on this, but has just started. The issue
>> (as I understand it) is that if there are systems where the ACPI tables are
>> only discoverable via EFI, then Xen+pvops will not be able to boot if pvops
>> doesn't have EFI run-time support. The following version of Xen won't come
>> out until probably Q2 2014, and won't hit distros probably until 6 months
>> after that.
>>
>> Given that, what do we think is the likelihood of such systems cropping up
>> in that timeframe? If the answer is anything other than "very low", I
>> think that as a strategic measure, this one is probably important enough to
>> slip the schedule a little bit if necessary.
> Except that this ought to be marked (external) in the first place:
> The hypervisor support is all there (otherwise our kernels wouldn't
> have been successfully booting on EFI for well over a year), and
> hence this work shouldn't really have any impact on the schedule.
Ah, right -- sorry, I misunderstood the situation. As long as the Xen
side is there to use as soon as the functionality is ready, I think
we're probably fine.
> The one feature here that requires work in our tree is to be able
> to boot via grub.efi (irrespective of how little I personally like that);
> I'm not sure Daniel was also planning to look into that part.
Do you think not having this for 4.3 will be a potential problem for Xen?
-George
next prev parent reply other threads:[~2013-01-23 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 16:32 4.3 Planning: Taking stock George Dunlap
2013-01-23 16:52 ` George Dunlap
2013-01-23 17:00 ` Jan Beulich
2013-01-23 17:10 ` George Dunlap [this message]
2013-01-24 8:32 ` Jan Beulich
2013-01-24 9:49 ` Ian Campbell
2013-01-24 10:03 ` Jan Beulich
2013-01-24 10:07 ` Ian Campbell
2013-01-24 10:43 ` Jan Beulich
2013-01-23 17:54 ` Konrad Rzeszutek Wilk
2013-01-24 8:33 ` Jan Beulich
2013-01-24 11:16 ` Daniel Kiper
2013-01-24 11:12 ` George Dunlap
2013-01-24 11:34 ` Daniel Kiper
2013-01-23 17:17 ` Thanos Makatos
2013-01-23 22:03 ` James Harper
2013-01-24 9:45 ` Ian Campbell
2013-01-24 11:48 ` James Harper
2013-01-24 12:57 ` Bastian Blank
2013-01-24 13:15 ` Ian Campbell
2013-01-23 17:05 ` Konrad Rzeszutek Wilk
2013-01-23 17:06 ` George Dunlap
2013-02-12 10:32 ` 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=51001986.7020301@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano@stabellini.net \
--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.