[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [Qemu-devel] [PATCH 13/13] xen: pv domain builder.

>> Patches 02 -> 04 pull depending patches, once you've merged with
>> upstream they are not needed any more and will be removed from the patch
>> set.
>> Patches 05 -> 09 is the backend core / console / framebuffer stuff you
>> are willing to take.
>> Patch 10 are the xen_machine_pv.c changes (upstream changeset has this
>> earlier, moved here for better bisectability).
>> Patch 11+ are disk + nic backends.  Ignore them if you don't want them.

> I'll take a more thorough look at 02-06.  Do they in your opinion make
> sense on their own in qemu-xen-unstable ?

02 -> 04  Make sense if you want to *test* the patches without merging
          with upstream qemu before.  For *merging* the patches I'd
          suggest to merge from upstream qemu instead, then wait for
          me rebasing the patchset (and dropping these patches).

05 -> 06  backend core.
07        switches the console to the new backend core.
08        xenfb.c -> xen_framebuffer.c rename.
09        switch framebuffer to new backend core.

05 + 06 alone are not useful as nobody uses the new backend core then.
Merging 07 too gives at least one user.  08+09 going in gives a second
user.  They are a nice cleanup and certainly make sense for


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.