From: Avi Kivity <avi@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] KVM: Avoid using CONFIG_ in userspace visible headers
Date: Mon, 19 Jan 2009 18:35:11 +0200 [thread overview]
Message-ID: <4974ABBF.8020600@redhat.com> (raw)
In-Reply-To: <20090119162947.GA10378@uranus.ravnborg.org>
Sam Ravnborg wrote:
> With the exported headers we at least have a clear definition
> what part of the headers are actually exported.
> So what we have now is a much better base to cut off from.
>
> And there is plenty of room for improvements but it requires
> someone with understanding of the kernel side and the user side to do
> this.
>
> I for once find it hard to judge what is really used by user space and
> not. Diving into glibc does not help as userspace is much more than
> glibc although glibc is an important 'customer' here.
>
If you set up an abi directory with clear guidelines and kbuild support,
actively maintained pieces could be moved by the maintainers. The rest
will continue to suck, but we will have improved the kernel a little bit.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-19 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 13:00 [PATCH] KVM: Avoid using CONFIG_ in userspace visible headers Avi Kivity
2009-01-19 13:09 ` Ingo Molnar
2009-01-19 13:12 ` Avi Kivity
2009-01-19 13:22 ` Ingo Molnar
2009-01-19 13:31 ` Avi Kivity
2009-01-19 16:29 ` Sam Ravnborg
2009-01-19 16:35 ` Avi Kivity [this message]
2009-01-19 16:32 ` Sam Ravnborg
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=4974ABBF.8020600@redhat.com \
--to=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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