From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, kvm <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Tue, 03 May 2011 19:39:25 +0200 [thread overview]
Message-ID: <4DC03DCD.30103@siemens.com> (raw)
In-Reply-To: <20110503173200.GA30864@laped.lan>
On 2011-05-03 19:32, Edgar E. Iglesias wrote:
> On Tue, May 03, 2011 at 08:13:04PM +0300, Avi Kivity wrote:
>> On 05/03/2011 08:09 PM, Jan Kiszka wrote:
>>>>
>>>> Reluctant ack.
>>>
>>> What downsides do you see?
>>
>> The usual "it shouldn't be this way". Every other package (including, I
>> think, glibc) uses the sanitized system headers. Except for kvm-kmod,
>> the system headers are always available.
>
> I agree, it doesn't feel quite right to bring in the headers. I don't have
> any alternative suggestions (besides better HOWTOs/Documentation) though.
Again, the downside of the current approach are:
- outdated distro headers silently disable features during build time
(happened to me with vhost e.g.)
- build breakages against older kernels / headers are pre-programmed
as hardly anyone tests all the possible combinations
- tons of #ifdef in the code + configure checks to catch the possible
combinations
Also note that [1] recommends this approach as well. I'm not aware of
good examples, but I would be fairly surprised if we were the first to
do this.
Jan
[1] http://kernelnewbies.org/KernelHeaders
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-03 17:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:05 [Qemu-devel] [RFC][PATCH] Import Linux headers for KVM and vhost Jan Kiszka
2011-05-03 15:12 ` Christoph Hellwig
2011-05-03 15:32 ` Jan Kiszka
2011-05-03 15:41 ` Arnd Bergmann
2011-05-03 16:48 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2011-05-03 16:55 ` Avi Kivity
2011-05-03 17:09 ` Jan Kiszka
2011-05-03 17:13 ` Avi Kivity
2011-05-03 17:32 ` Edgar E. Iglesias
2011-05-03 17:39 ` Jan Kiszka [this message]
2011-05-03 17:57 ` Scott Wood
2011-05-03 19:26 ` Arnd Bergmann
2011-05-03 17:30 ` Peter Maydell
2011-05-03 17:42 ` Jan Kiszka
2011-05-03 17:45 ` Anthony Liguori
2011-05-03 17:55 ` Jan Kiszka
2011-05-03 17:59 ` Anthony Liguori
2011-05-03 21:37 ` Michael S. Tsirkin
2011-05-04 8:55 ` Jan Kiszka
2011-05-09 3:24 ` Rusty Russell
2011-05-03 20:22 ` Peter Maydell
2011-05-04 10:28 ` Jan Kiszka
2011-05-04 17:58 ` Andreas Färber
2011-05-04 18:01 ` Jan Kiszka
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=4DC03DCD.30103@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).