From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [RFC] Bring in all the Linux headers we depend on in QEMU
Date: Mon, 04 May 2009 08:24:13 -0500 [thread overview]
Message-ID: <49FEEC7D.8090601@codemonkey.ws> (raw)
In-Reply-To: <49FEB0A6.4080104@redhat.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Comments?
>>
>
> Thinking again about it, this is not really necessary.
>
> In general a distro provides kernel headers matched to the running
> kernel. For example F10 provides
> kernel-headers-2.6.27.21-170.2.56.fc10.x86_64 to go along with
> kernel-2.6.27.21-170.2.56.fc10.x86_64. So a user running a distro
> kernel (the majority, given that most people don't inflict pain upon
> themselves unnecessarily) will have exactly the features exported by
> the kernel.
kernel-headers is not usually installed by default. Also, I'd rather
not deal with #ifdef code as we introduce new features like TUN_VNET_HDR.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-04 13:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 21:37 [Qemu-devel] [RFC] Bring in all the Linux headers we depend on in QEMU Anthony Liguori
2009-05-04 6:51 ` Stefan Weil
2009-05-04 8:17 ` Edgar E. Iglesias
2009-05-04 13:15 ` Anthony Liguori
2009-05-04 13:44 ` Edgar E. Iglesias
2009-05-04 13:13 ` Anthony Liguori
2009-05-04 13:28 ` Avi Kivity
2009-05-04 13:30 ` Anthony Liguori
2009-05-04 14:01 ` Christoph Hellwig
2009-05-04 14:27 ` Lennart Sorensen
2009-05-04 7:52 ` Avi Kivity
2009-05-04 9:35 ` Paul Brook
2009-05-04 13:14 ` Anthony Liguori
2009-05-04 9:08 ` [Qemu-devel] " Avi Kivity
2009-05-04 12:42 ` Mark McLoughlin
2009-05-04 13:01 ` Arnd Bergmann
2009-05-04 13:25 ` Anthony Liguori
2009-05-04 13:26 ` Avi Kivity
2009-05-04 13:24 ` Anthony Liguori [this message]
2009-05-04 13:40 ` Avi Kivity
2009-05-04 11:29 ` Arnd Bergmann
2009-05-04 13:21 ` Anthony Liguori
2009-05-04 13:38 ` Avi Kivity
2009-05-04 14:04 ` Christoph Hellwig
2009-05-04 14:18 ` Arnd Bergmann
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=49FEEC7D.8090601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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).