From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Rientjes <rientjes@google.com>,
David Woodhouse <dwmw2@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <levinsasha928@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Pekka Enberg <penberg@kernel.org>, Michal Marek <mmarek@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)
Date: Mon, 11 Feb 2013 18:58:56 +0100 [thread overview]
Message-ID: <20130211175856.GC9716@gmail.com> (raw)
In-Reply-To: <CA+55aFx-0-qcYMqH2wnJJ7iAPhoEvD_EQ0xqVW3VGS3G9=_1_w@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Feb 11, 2013 9:28 AM, "Ingo Molnar" <mingo@kernel.org> wrote:
>
> > How on earth can anyone, against all that evidence, still
> > claim that it's a net minus?
>
> Because I don't think there is any reason for mixing up the
> projects. Why do you not just make it separate? Everything you
> claim is such a big deal would still work perfectly well.
>
> Every time you talk about "negative" it's as of the project
> wouldn't exist if it was external. Which is total bull, since
> it is effectively external already. [...]
That's not actually true. If you check the list of early
tools/kvm/ contributors you will see an overlap with -tip
contributors. I know tools/kvm/ developers who just use their
existing -tip repo to pick up the latest. They are using the
-tip commit notifications to see what went in and what not, etc.
Claiming that because the contribution model works to a certain
degree integrated into a small Linux subsystem tree it does not
ever have to go upstream is so wrong on so many levels ...
The most likely correct statement would be something like: "if
it worked on a small scale it will probably work even better
with more exposure on a larger scale." We'll never know that
though.
( That is also why some of the focus was on lockdep - knowing
that it's close in terms of maintenance distance made it an
easier topic - socially. )
Since I'm using it on an almost daily basis to test out failed
bzImages, and because I (mistakenly) thought it had some
upstream chances, I found it good to help out (a bit) with
maintenance and code review.
While it works it's obviously limited - there's just so many
-tip developers and I thought everyone would benefit from this
going the next natural step.
> [...] And it will stay that way. You are just in denial and
> trying to say that integrating it would somehow help.
>
> And I claim it wouldn't. It works fine outside already. Just
> ADMIT it.
So tools/kvm/ works 'just fine' - in its current limited form -
because for the developers involved it's already "upstream", for
the first hop of upstream.
So basically Pekka optimistically thought it's an eventual 'tit
for tat', a constant stream of benefits to the kernel, in the
hope of finding a home in the upstream kernel which would
further help both projects. The kernel wants to keep the 'tit'
only though.
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-11 17:59 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 21:51 [PATCH] x86: Default to ARCH=x86 to avoid overriding CONFIG_64BIT David Woodhouse
2012-12-21 2:07 ` [tip:x86/build] x86: Default to ARCH= x86 " tip-bot for David Woodhouse
2012-12-26 6:32 ` David Rientjes
2012-12-26 8:43 ` David Woodhouse
2012-12-26 10:44 ` David Rientjes
2012-12-26 12:38 ` David Woodhouse
2012-12-26 22:00 ` David Rientjes
2012-12-26 22:19 ` David Woodhouse
2012-12-27 1:52 ` David Rientjes
2012-12-27 8:01 ` David Woodhouse
2012-12-26 22:30 ` Jesper Juhl
2012-12-26 23:07 ` David Woodhouse
2012-12-26 23:13 ` H. Peter Anvin
2012-12-26 23:32 ` [tip] config: Add 'make kvmconfig' David Woodhouse
2012-12-27 1:08 ` Randy Dunlap
2013-02-04 18:20 ` [patch] config: fix make kvmconfig David Rientjes
2013-02-04 18:44 ` Ingo Molnar
2013-02-04 18:57 ` David Rientjes
2013-02-04 19:11 ` Ingo Molnar
2013-02-04 19:14 ` Greg Kroah-Hartman
2013-02-04 19:13 ` Ingo Molnar
2013-02-06 18:25 ` Pekka Enberg
2013-02-06 20:12 ` David Rientjes
2013-02-06 20:45 ` Pekka Enberg
2013-02-06 21:02 ` kvmtool tree (Was: Re: [patch] config: fix make kvmconfig) Stephen Rothwell
2013-02-06 21:46 ` Ingo Molnar
2013-02-06 21:55 ` H. Peter Anvin
2013-02-07 21:44 ` Stephen Rothwell
2013-02-07 21:40 ` Stephen Rothwell
2013-02-08 14:55 ` Ingo Molnar
2013-02-08 21:14 ` Linus Torvalds
2013-02-08 23:57 ` Pekka Enberg
2013-02-09 0:45 ` Linus Torvalds
2013-02-09 10:01 ` Pekka Enberg
2013-02-09 18:07 ` Linus Torvalds
2013-02-09 19:39 ` Pekka Enberg
2013-02-09 19:57 ` Linus Torvalds
2013-02-09 21:06 ` Theodore Ts'o
2013-02-11 12:38 ` Ingo Molnar
2013-02-11 12:26 ` Ingo Molnar
2013-02-11 12:56 ` Ingo Molnar
2013-02-11 13:18 ` David Woodhouse
2013-02-11 13:58 ` Anca Emanuel
2013-02-11 16:34 ` Linus Torvalds
2013-02-11 17:34 ` H. Peter Anvin
2013-02-11 17:41 ` Ingo Molnar
2013-02-11 14:47 ` Pekka Enberg
2013-02-11 16:46 ` David Woodhouse
2013-02-11 17:26 ` Anca Emanuel
2013-02-11 16:32 ` Linus Torvalds
2013-02-11 17:28 ` Ingo Molnar
[not found] ` <CA+55aFx-0-qcYMqH2wnJJ7iAPhoEvD_EQ0xqVW3VGS3G9=_1_w@mail.gmail.com>
2013-02-11 17:58 ` Ingo Molnar [this message]
2013-02-11 23:32 ` Linus Torvalds
2013-02-12 9:52 ` Ingo Molnar
2013-02-13 8:23 ` Paolo Bonzini
2013-02-13 8:56 ` Pekka Enberg
2013-02-13 9:23 ` Ingo Molnar
2013-02-14 15:32 ` Anthony Liguori
2013-02-19 8:08 ` Ingo Molnar
2013-01-12 17:06 ` [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding CONFIG_64BIT Borislav Petkov
2013-01-12 17:40 ` H. Peter Anvin
2013-01-12 18:08 ` Borislav Petkov
2013-01-12 18:10 ` H. Peter Anvin
2013-04-12 16:01 ` [PATCH] x86: Default to ARCH=x86 " richard -rw- weinberger
2013-04-12 16:38 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130211175856.GC9716@gmail.com \
--to=mingo@kernel.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.