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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100322173923.GA25498@elte.hu>
Date:	Mon, 22 Mar 2010 18:39:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Avi Kivity <avi@...hat.com>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Joerg Roedel <joro@...tes.org>,
	Anthony Liguori <anthony@...emonkey.ws>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Sheng Yang <sheng@...ux.intel.com>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Jes Sorensen <Jes.Sorensen@...hat.com>,
	Gleb Natapov <gleb@...hat.com>,
	Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Fr?d?ric Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
 project


* Avi Kivity <avi@...hat.com> wrote:

> On 03/22/2010 07:27 PM, Pekka Enberg wrote:
> >
> > It's kinda funny to see people argue that having an external repository is 
> > not a problem and that it's not a big deal if building something from the 
> > repository is slightly painful as long as it doesn't require a PhD when we 
> > have _real world_ experience that it _does_ limit developer base in some 
> > cases. Whether or not that applies to kvm remains to be seen but I've yet 
> > to see a convincing argument why it doesn't.
> 
> qemu has non-Linux developers.  Not all of their contributions are relevant 
> to kvm but some are.  If we pull qemu into tools/kvm, we lose them.

Qemu had very few developers before KVM made use of it - i know it because i 
followed the project prior KVM.

So whatever development activitity Qemu has today, it's 99% [WAG] attributable 
to KVM. It might have non-Linux contributors, but they wouldnt be there if it 
wasnt for all the Linux contributors ...

Furthermore, those contributors wouldnt have to leave - they could simply use 
a different Git URI ...

	Ingo
--
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/