[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111104161329.GO1512@8bytes.org>
Date: Fri, 4 Nov 2011 17:13:29 +0100
From: Joerg Roedel <joro@...tes.org>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: Pekka Enberg <penberg@...nel.org>,
Christoph Hellwig <hch@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Avi Kivity <avi@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
On Fri, Nov 04, 2011 at 03:42:22PM +0100, Jan Kiszka wrote:
> On 2011-11-04 14:32, Pekka Enberg wrote:
> > I know you don't see the benefits of integrated code base but I as a
> > developer do.
>
> IIRC, this discussion still lacks striking, concrete examples from the
> KVM tool vs. QEMU development processes.
How does it matter? KVM tool does not compete with QEMU. The use
cases for both programs are different. KVM tool is a helper for kernel
developers during development and additionally good example code on how
to use the KVM kernel interface (because it focuses on KVM only while
QEMU is much more than a KVM userspace).
Therefore it makes sense for KVM tool to be developed in the kernel tree
while it doesn't make sense for QEMU.
Regards,
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists