Re: [RFC] Unify KVM kernel-space and user-space code into a single project

[Olivier Galibert]

On Mon, Mar 22, 2010 at 03:54:37PM +0100, Ingo Molnar wrote:
> Yes, i thought Qemu would be a prime candidate to be the baseline for 
> tools/kvm/, but i guess that has become socially impossible now after this 
> flamewar. It's not a big problem in the big scheme of things: tools/kvm/ is 
> best grown up from a small towards larger size anyway ...

I'm curious, where would you put the limit?  Let's imagine a tools/kvm
appears, be it qemu or not, that's outside the scope of my question.
Would you put the legacy PC bios in there (seabios I guess)?  The EFI
bios? The windows-compiled paravirtual drivers? The Xorg paravirtual
DDX ?  Mesa (which includes the pv gallium drivers)? The
libvirt-equivalent? The GUI?

That's not a rhetorical question btw, I really wonder where the limit
should be.

  OG.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/