qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Bring in all the Linux headers we depend on in	QEMU
Date: Mon, 04 May 2009 16:28:16 +0300	[thread overview]
Message-ID: <49FEED70.7020606@redhat.com> (raw)
In-Reply-To: <49FEE9EC.6060604@codemonkey.ws>

Anthony Liguori wrote:
> Stefan Weil wrote:
>> Anthony Liguori schrieb:
>>  
>> For Debian systems, those headers are installed by package 
>> linux-libc-dev.
>> There are also packages for cross compilation in emdebian
>> (linux-libc-dev-mips-cross, linux-libc-dev-powerpc-cross, ...).
>>
>> Yes, those headers did not always match the features of the current 
>> kernel,
>> so --enable-kvm did not work. This is fixed now - there is a 
>> linux-libc-dev
>> 2.6.29-3 which is up-to-date.
>>
>> So, at the moment I see no need to fill the QEMU source tree with
>> linux header files.
>>   
>
> We can not just rely on everyone who uses QEMU to use the latest 
> version of Debian...
>
> The fact is, linux-libc-dev is *not* meant for applications to use as 
> the official kernel ABI.  We shouldn't depend on it.

At least on Fedora, kernel-headers is.  It is installed in 
/usr/include/linux and is synced (sorta) to the installed kernel.

Carrying a subset of kernel headers is a bit too much, IMO.

kvm is a special case since it is available externally.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-05-04 13:29 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 [this message]
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
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=49FEED70.7020606@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).