From: Christoph Hellwig <hch@infradead.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
Date: Fri, 4 Nov 2011 09:02:25 -0400 [thread overview]
Message-ID: <20111104130225.GA24563@infradead.org> (raw)
In-Reply-To: <CAOJsxLGf78q7rR7-q4d6TizmghFcKyK3tFOAew4i2-SHrZcvhQ@mail.gmail.com>
On Fri, Nov 04, 2011 at 02:35:18PM +0200, Pekka Enberg wrote:
> We are reusing kernel code and headers and I am not interested in
> copying them over. Living in the kernel tree is part of the design,
> whether you like it or not.
That's pretty much a blanko argument for throwing everything into the
kernel. What's next, throwing your jvm into the kernel because you like
some kernel helpers?
We've been through this a few times - there is no reason why a tool
using the KVM ioctls should be considered close to the kernel - all
other users get away just fine staying out of tree, and that has
helped to keep the ABI stable.
This sounds more like you should create a libkernelutil with useful
data structures we use in the kernel for userspace programs. I'd love
to use that for a few projects, btw.
next prev parent reply other threads:[~2011-11-04 13:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 12:35 ` Pekka Enberg
2011-11-04 13:02 ` Christoph Hellwig [this message]
2011-11-04 13:32 ` Pekka Enberg
2011-11-04 14:42 ` Jan Kiszka
2011-11-04 15:16 ` Sasha Levin
2011-11-04 16:26 ` Jan Kiszka
2011-11-04 16:48 ` Sasha Levin
2011-11-04 17:33 ` Jan Kiszka
2011-11-04 16:13 ` Joerg Roedel
2011-11-04 16:42 ` Jan Kiszka
2011-11-04 17:41 ` Pekka Enberg
2011-11-04 13:14 ` Joerg Roedel
2011-11-04 14:47 ` Jan Kiszka
2011-11-08 14:44 ` richard -rw- weinberger
2011-11-08 15:36 ` Pekka Enberg
2011-11-08 16:00 ` richard -rw- weinberger
2011-11-10 3:50 ` Anthony Liguori
2011-11-10 6:46 ` Pekka Enberg
2011-11-10 7:57 ` Markus Armbruster
2011-11-10 8:21 ` Pekka Enberg
2011-11-10 8:23 ` Sasha Levin
2011-11-10 8:28 ` Pekka Enberg
2011-11-10 8:57 ` Markus Armbruster
2011-11-10 9:04 ` Sasha Levin
2011-11-10 9:09 ` Avi Kivity
2011-11-10 9:14 ` Sasha Levin
2011-11-10 9:23 ` Avi Kivity
2011-11-10 9:34 ` Sasha Levin
2011-11-10 9:43 ` Avi Kivity
2011-11-10 9:49 ` Sasha Levin
2011-11-10 9:50 ` Avi Kivity
2011-11-10 9:48 ` Markus Armbruster
2011-11-10 13:43 ` Anthony Liguori
2011-11-10 13:56 ` Pekka Enberg
2011-11-10 14:47 ` Markus Armbruster
2011-11-10 15:33 ` Stefan Hajnoczi
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=20111104130225.GA24563@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--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