Re: [Xen-devel] [PATCH 0/8] 2.6.17 merge additions

[Keir Fraser <keir@xxxxxxxxxxxxx>]

On 2/3/07 09:05, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Before submitting 2.6.18 stuff we were missing from the -unstable merge,
> is it possible to get an understanding why patches 5 (pc speaker device
> registration in domU) and 8 (early DMI scan) of the 2.6.17 set were not
> taken?

I'm undecided on those. Keeping pcspkr is pretty harmless (actually I'm not
sure what the device registration is even for!) and removing it would just
take us further from native. I don't have a really strong opinion on this
one however. For the second patch: the principle of moving DMI scan earlier
is nice, but this approach makes a horrible mess of the mm init code (which
is quite nasty enough already!). I wonder whether we could come up with a
two-stage mm init for x86/64 -- some very early Xen-specific stuff to get is
into a state that is a bit more like native, would allow us to do things
like DMI scan at a more appropriate time, and might clean up the
paging_init() mess a bit rather than making it worse.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel