From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pekka Enberg <penberg@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
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>, 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 13:56:27 +0100 [thread overview]
Message-ID: <20130211125627.GA7583@gmail.com> (raw)
In-Reply-To: <20130211122654.GA5802@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> [...]
>
> - he ended up gradually validating whether lockdep could be
> ported to user-space. He first used 'messy' integration:
> kernel/lockdep.c hacked up badly and linked directly into
> user-space app. Then he did 'clean' integration: some
> modifications to kernel/lockdep.c enabled it to be
> librarified, and then the remaining work was done in
> user-space - here too in successive steps.
>
> - tools/kvm/ happened to be hosted in the same kernel repo
> that the locking tree is hosted in.
>
> The end result is something good that I never saw happen to
> kernel code before, in the last 20 years of the Linux kernel.
> Maybe it could have happened with an outside tools/kvm repo,
> but I very strongly suspect that it would not.
>
> In theory this could have been done in the cold, fragmented,
> isolated and desolate landscape of Linux user-space utilities,
> by copying kernel/lockdep.c and a handful of kernel headers to
> user-space, and making it work there somehow.
>
> Just like a blue rose could in theory grow on Antarctica as
> well, given the right set of circumstances. It just so happens
> that blue roses best grow in Holland, where there's good
> support infrastructure for growing green stuff, while you'd
> have to look hard to find any green stuff at all on
> Antarctica.
To use another, perhaps more applicable analogy:
If one has the choice to start a new business in the U.S., it
would be reasonable to do that. There's a lot of supporting
infrastructure, trust, distribution, standards, enforcement
agencies and available workers.
Could the same business succeed in Somalia as well? Possibly -
if it's a bakery or something similarly fundamental. More
complex businesses would likely not thrive very well there.
*That* is how I think the current Linux kernel tooling landscape
looks like currently in a fair number of places: in many aspects
it's similar to Somalia - disjunct entities with not much
commonality or shared infrastructure.
Why people question the desire for a kernel related project
(that only runs on a Linux host) to actually be part of an
already well working, civilized society (the kernel repo) - for
mutual, well documented benefits - instead of having to grow it
all itself, is rather perplexing to me...
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-11 12:56 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 [this message]
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
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=20130211125627.GA7583@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome