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: <20121018100312.GB14814@gmail.com>
Date:	Thu, 18 Oct 2012 12:03:12 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Pekka Enberg <penberg@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0


* Christoph Hellwig <hch@...radead.org> wrote:

> On Fri, Oct 12, 2012 at 02:34:33PM +0300, Pekka Enberg wrote:
> > Hi Linus,
> > 
> > Please consider pulling the latest LKVM tree from:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
> > 
> > LKVM is the long lost userspace friend of KVM that makes it really easy
> > to launch virtualized Linx environment on x86 and PPC64 Linux.
> 
> This still doesn't have any business in the kernel tree. [...]

Pekka & the LKVM developers are using the tools/kvm/ tree setup 
to create new kernel features, to improve the kernel and to 
reuse kernel code, amongst other things.

So being in the kernel tree is very practical and useful to 
them.

It's also *very* useful to kernel developers like me, and I wish 
all of user-space tooling was as easy to use and as well working 
as 'vm run':

I'm using 'vm' regularly for quick kernel testing: I just want 
something that just works and reuses the existing distro 
user-space environment unintrusively. In that sense it's very 
handy, 'vm' will in essence boot the well-maintained system. Not 
some stale old disk image. Not a second system I need to 
maintain. I'd not be using it if it didn't came integrated via 
tools/ and integrated into the kernel. 'make kvmconfig' and the 
other bits of practical kernel development integration are very 
useful and just work as well.

The fact that it's not useful to you (yet?) that does not 
invalidate the utility of this project to those to whom it *is* 
useful. No argument you ever outlined here invalidates the plain 
utility of this project.

Whether you think that it "has no place in the kernel" is 
completely irrelevant - what matters is actual utility to 
people:

If Linus thinks that the upsides are not convincing enough (yet, 
or ever), that's obviously enough reason for him to not pull it 
- but that does not stop this project from being useful to those 
who *are* using it to improve and test the kernel.

Thanks,

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ