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 for Android: free password hash cracker in your pocket

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

Message-ID: <4BA7B098.60205@redhat.com>
Date:	Mon, 22 Mar 2010 20:02:00 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
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

On 03/22/2010 07:43 PM, Ingo Molnar 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.
>>      
> Yeah.
>
> Also, if in fact the claim that the 'repository does not matter' is true then
> it doesnt matter that it's hosted in tools/kvm/ either, right?
>    

Again, the second it's moved to tools/kvm/ we strip it off anything that 
kvm can't use.

> I.e. it's a win-win situation. Worst-case nothing happens beyond a Git URI
> change. Best-case the project is propelled to never seen heights due to
> contribution advantages not contemplated and not experienced by the KVM guys
> before ...
>    

You're exaggerating.  There were 773 commits into qemu.git (excluding 
qemu-kvm.git) in the past three months.  162 for the same period for 
tools/perf.  The pool is not that deep.

-- 
error compiling committee.c: too many arguments to function

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