On 07/28/09 21:14, Brown, Len wrote:
> Does somebody expect all this dom0 stuff to really live
> in the upstream linux kernel source tree?
>
The control domain (dom0) patches are held up by a very specific set of
concerns that I'm working on now. I don't think there's any fundamental
reason it won't make it in at some point, and there's no reason not to
lay the groundwork in the meantime.
These acpi patches are very useful, but not essential functionality.
I'd like to see them evolve along lines that are acceptable to everyone
before making a serious push upstream.
> s/extcntl/xen/ to make it clear why this code exists --
> or is there an expected "external control" other than Xen?
>
I dislike making Xen-specific changes. Ideally we can find a way to fit
these changes into some other abstraction which already exists, or if
added would be useful to more than one user.
J
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
