linux-kernel - Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

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: <CA+55aFwq+_TvOZNEPO-eFPjYuPuMFL0bgR0x=nLq_tvfATqaTA@mail.gmail.com>
Date:	Mon, 11 Feb 2013 08:32:59 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Pekka Enberg <penberg@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Randy Dunlap <rdunlap@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	David Rientjes <rientjes@...gle.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>, Michal Marek <mmarek@...e.cz>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

On Mon, Feb 11, 2013 at 4:26 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> If you are asking whether it is critical for the kernel project
> to have tools/kvm/ integrated then it isn't. The kernel will
> live just fine without it, even if that decision is a mistake.

You go on to explain how this helps kvmtool, and quite frankly, I DO NOT CARE.

Everything you talk about is about helping your work, by making the
kernel maintenance be more. The fact that you want to use kernel
infrastructure in kvmtool is a great example: you may think it's a
great thing, but for the kernel it's just extra work, and extra layers
of abstraction etc etc.

And then you make it clear that you haven't even *bothered* to try to
make it a separate project.

Sorry, but with that kind of approach, I get less and less interested.
I think this whole tying together is a big mistake. It encourages
linkages that simply shouldn't be there.

And no, perf is not the perfect counter-example. With perf,. the
linkages made sense! There's supposed to be deep linkages to profiling
and event counting. There is ABSOLUTELY NOT supposed to be deep
linkages with virtualization. Quite the reverse.

And no, I don't want to maintain the mess that is both. There's just
no gain, and lots of potential pain.

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