Message-ID: <CA+55aFzXF-4Xwc4HU8vnTin4WqtvYcpXq0TsqTN_vRg=myLH_Q@mail.gmail.com>
Date:	Sun, 10 Feb 2013 06:57:41 +1100
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	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>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

On Sun, Feb 10, 2013 at 6:39 AM, Pekka Enberg <penberg@...nel.org> wrote:
>
> The main argument for merging into the main kernel repository has always been
> that (we think) it improves the kernel because significant amount of
> development is directly linked to kernel code (think KVM ARM port here, for
> example). The secondary argument has been to make it easy for kernel developers
> to work on both userspace and kernel in tandem (like has happened with vhost
> drivers). In short: it speeds up development of Linux virtualization code.

Why? You've made this statement over and over and over again, and I've
dismissed it over and over and over again because I simply don't think
it's true.

It's simply a statement with nothing to back it up. Why repeat it?

THAT is my main contention. I told you why I think it's actually
actively untrue. You claim it helps, but what is it about kvmtool that
makes it so magically helpful to be inside the kernel repository? What
is it about this that makes it so critical that you get the kernel and
kvmtool with a single pull, and they have to be in sync? When you then
at the same time claim that you make very sure that they don't have to
be in sync at all. See your earlier emails about how you claim to have
worked very hard to make sure they work across different versions.

So you make these unsubstantiated claims about how much easier it is,
and they make no sense. You never explain *why* it's so magically
easier. Is git so hard to use that you can't do "git pull" twice? And
why would you normally even *want* to do git pull twice? 99% of the
work in the kernel has nothing what-so-ever to do with kvmtool, and
hopefully the reverse is equally true.

And tying into the kernel just creates this myopic world of only
looking at the current kernel. What if somebody decides that they
actually want to try to boot Windows with kvmtool? What if somebody
tells you that they are really tired of Xen, and actually want to turn
kvmtool into  *replacement* for Xen instead? What if somebody wants to
branch off their own work, concentrating on some other issue entirely,
and wants to merge with upstream kvmtool but not worry about the
kernel, because they aren't working on the Linux kernel at all, and
their work is about something else?

I just don't think it makes sense. I don't see what the huge advantage
of a single git tree is.

Anyway, I'm done arguing. You can do what you want, but just stop
misrepresenting it as being "linux-next" material unless you are
willing to actually explain why it should be so.

                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/

Powered by blists - more mailing lists