On 11/01/2010 02:47 PM, Alexander Graf wrote:
Where else would it belong? Qemu is an emulator. Device emulation belongs to
qemu code. The xen PV machine is nothing but a special case of the pc machine
with custom firmware and odd devices :).
As I stated in my cover letter, the goal of all this should be to have the qemu
pieces be 100% independent of any xen headers or libraries,
I'm not sure I agree with the goal. I think where ever possible we
should reuse code with the Xen project when it makes sense. Reusing
blkback/netback is impossible because we want userspace implementations
and the current implementations are in the kernel. blktap also doesn't
tie into the QEMU block layer and making it tie into the QEMU block
layer would probably result in more code than it saved.
OTOH, xenstored and xenconsoled have very little direct dependence on
Xen. I'm not saying that we shouldn't make things Just Work in QEMU, so
if that means spawning xenconsoled/xenstored automagically from QEMU
with special options, that's perfectly fine.
But to replicate the functionality of this code solely because of NIH
seems like a waste of effort.
Regards,
Anthony Liguori
so we can eventually isolate it well enough that it even works on non-x86.
Then we're at the point qemu code usually is.
I'm sure there are also practical implications btw. But I don't really care
about those too much, because the architectural ones outweigh that to me.
Alex
