linux-kernel - Re: [RFC/GIT PULL] Linux KVM tool for v3.2

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: <20111104131436.GN1512@8bytes.org>
Date:	Fri, 4 Nov 2011 14:14:36 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Avi Kivity <avi@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2

On Fri, Nov 04, 2011 at 02:35:18PM +0200, Pekka Enberg wrote:
> We are reusing kernel code and headers and I am not interested in
> copying them over. Living in the kernel tree is part of the design,
> whether you like it or not.

Besides that the KVM tool with its small and clean code-base is a really
nice reference on how to use the KVM kernel interface for anyone willing
to implement its own user-space. As a developer you can learn a lot more
from it as by reading the files on Documentation/.  So I think it should
definitly be part of the kernel source tree.

Whether it lives in tools/ or Documentation/ ... I don't care. In tools/
is certainly better for all the developers already using the it for
testing their kernels.

Regards,

	Joerg

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