linux-kernel - Re: [GIT PULL] Native Linux KVM tool for 3.1

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: <83392120-2809-429C-A75F-9A23E25B1A56@suse.de>
Date:	Mon, 25 Jul 2011 15:29:56 +0200
From:	Alexander Graf <agraf@...e.de>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Avi Kivity <avi@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Jan Kiszka <jan.kiszka@....de>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org, gorcunov@...il.com, levinsasha928@...il.com,
	asias.hejun@...il.com, prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1


On 25.07.2011, at 15:09, Pekka Enberg wrote:

> Hi Alexander,
> 
> On Mon, 2011-07-25 at 14:51 +0200, Alexander Graf wrote:
>> And if you need to share code with perf, then that just proves the
>> point that perf doesn't belong inside the kernel tree either.
> 
> You seem to want to prove something here but our reasoning is based on
> experience and practicalities - not some theoretical idea what should
> and what shouldn't be in the Linux kernel tree. I really don't think
> that perf would have turned out to be as useful as it is if it was
> developed out-of-the-tree.

IIUC that was mainly because the interface is very very closely coupled with kernel code.

> That's also why we think tools/kvm is such a good idea.

I like pears, so I like apples too?


Alex

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