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]

Date:	Mon, 22 Mar 2010 18:43:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	"Frank Ch. Eigler" <fche@...hat.com>,
	Joerg Roedel <joro@...tes.org>, Avi Kivity <avi@...hat.com>,
	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


* Pekka Enberg <penberg@...helsinki.fi> wrote:

> Hi Frank,
> 
> On Mon, Mar 22, 2010 at 7:17 PM, Frank Ch. Eigler <fche@...hat.com> wrote:
> > In your very previous paragraphs, you enumerate two separate causes:
> > "repository structure" and "development/maintenance process" as being
> > sources of "fun". ?Please simply accept that the former is considered
> > by many as absolutely trivial compared to the latter, and additional
> > verbose repetition of your thesis will not change this.
> 
> I can accept that many people consider it trivial but the problem is that we 
> have _real data_ on kmemtrace and now perf that the amount of contributors 
> is significantly smaller when your code is outside the kernel repository. 
> Now admittedly both of them are pretty intimate with the kernel but Ingo's 
> suggestion of putting kvm-qemu in tools/ is an interesting idea 
> nevertheless.

Correct.

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

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

	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/