[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH for-xen-4.5 v4 00/18] xen: Break multiboot (v1) dependency and add multiboot2 support
- To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- From: konrad wilk <konrad.wilk@xxxxxxxxxx>
- Date: Thu, 23 Oct 2014 14:04:51 -0400
- Cc: Juergen Gross <JGross@xxxxxxxx>, keir@xxxxxxx, ian.campbell@xxxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, Daniel Kiper <daniel.kiper@xxxxxxxxxx>, ross.philipson@xxxxxxxxxx, roy.franz@xxxxxxxxxx, ning.sun@xxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, qiaowei.ren@xxxxxxxxx, richard.l.maliszewski@xxxxxxxxx, gang.wei@xxxxxxxxx, fu.wei@xxxxxxxxxx
- Delivery-date: Thu, 23 Oct 2014 18:10:16 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
Furthermore, there is still an open question of whether "unify all boot
paths" is indeed a clever idea in the first place. Again, this is
ideally something which should have been argued over / decided upon as
part of the design review. (People on the list might notice a
reoccurring theme there, when it comes to doing large chunks of work.)
And it _was_ discussed at the Xen hackathon multiple times - where it
seems it was the perfect place to hash this out.
Or are we saying that any big project in Xen MUST have a design document
with it? If so we really need to document that somewhere.
This is frustrating.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
