From: Jan Kiszka <jan.kiszka@siemens.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Pekka Enberg <penberg@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
Date: Fri, 04 Nov 2011 17:42:07 +0100 [thread overview]
Message-ID: <4EB415DF.3050906@siemens.com> (raw)
In-Reply-To: <20111104161329.GO1512@8bytes.org>
On 2011-11-04 17:13, Joerg Roedel wrote:
> 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.
I'm still under the impression that it will start to compete for the
reference implementation of KVM changes. I might see ghosts, but I
surely do not want to see this happen for many reasons.
> The use cases for both programs are different.
Really?
> KVM tool is a helper for kernel
> developers during development
Well, 'make' is a helper for kernel development as well...
> 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).
[ If this is architecturally good or bad would be worth a separate
discussion. ]
> Therefore it makes sense for KVM tool to be developed in the kernel tree
> while it doesn't make sense for QEMU.
And I disagree regarding KVM tool based on the arguments brought forward
so far.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-11-04 16:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 12:35 ` Pekka Enberg
2011-11-04 13:02 ` Christoph Hellwig
2011-11-04 13:32 ` Pekka Enberg
2011-11-04 14:42 ` Jan Kiszka
2011-11-04 15:16 ` Sasha Levin
2011-11-04 16:26 ` Jan Kiszka
2011-11-04 16:48 ` Sasha Levin
2011-11-04 17:33 ` Jan Kiszka
2011-11-04 16:13 ` Joerg Roedel
2011-11-04 16:42 ` Jan Kiszka [this message]
2011-11-04 17:41 ` Pekka Enberg
2011-11-04 13:14 ` Joerg Roedel
2011-11-04 14:47 ` Jan Kiszka
2011-11-08 14:44 ` richard -rw- weinberger
2011-11-08 15:36 ` Pekka Enberg
2011-11-08 16:00 ` richard -rw- weinberger
2011-11-10 3:50 ` Anthony Liguori
2011-11-10 6:46 ` Pekka Enberg
2011-11-10 7:57 ` Markus Armbruster
2011-11-10 8:21 ` Pekka Enberg
2011-11-10 8:23 ` Sasha Levin
2011-11-10 8:28 ` Pekka Enberg
2011-11-10 8:57 ` Markus Armbruster
2011-11-10 9:04 ` Sasha Levin
2011-11-10 9:09 ` Avi Kivity
2011-11-10 9:14 ` Sasha Levin
2011-11-10 9:23 ` Avi Kivity
2011-11-10 9:34 ` Sasha Levin
2011-11-10 9:43 ` Avi Kivity
2011-11-10 9:49 ` Sasha Levin
2011-11-10 9:50 ` Avi Kivity
2011-11-10 9:48 ` Markus Armbruster
2011-11-10 13:43 ` Anthony Liguori
2011-11-10 13:56 ` Pekka Enberg
2011-11-10 14:47 ` Markus Armbruster
2011-11-10 15:33 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB415DF.3050906@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.