From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: kvm headers update
Date: Thu, 08 Oct 2009 15:39:56 +0200 [thread overview]
Message-ID: <4ACDEBAC.10200@redhat.com> (raw)
In-Reply-To: <200910061909.29977.arnd@arndb.de>
On 10/06/2009 07:09 PM, Arnd Bergmann wrote:
> On Tuesday 06 October 2009, Avi Kivity wrote:
>
>> On 10/05/2009 09:27 PM, Michael S. Tsirkin wrote:
>>
>>>
>>>
>>>> Or is this the output of 'make headers_install'?
>>>>
>>>>
>>> yes. I just added include to kvm_types to add the CONFIG_ stuff.
>>> Or maybe instead we should fix users to depend on the correct ifdefs.
>>>
>>>
>>>
>> I think 'make headers_install' results in non-portable headers since it
>> unifdefs stuff out.
>>
> The point of 'make headers_install' is to turn kernel headers into
> user space headers, e.g. removing address space annotations
> that are undefined in user space but required in the kernel.
>
> Unifdef only removes parts under #ifdef __KERNEL__, and by extension,
> anything under CONFIG_*, which is not allowed outside of __KERNEL__,
> because it may have an entirely different meaning in user space.
>
> So, for building qemu, we should really use a copy of the 'installed'
> version, but of course not for building the external module.
>
Yeah - kvm headers used to depend on CONFIG_*, but looks like this was
fixed (by me - oh my memory).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-10-08 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 9:46 [PATCH] qemu-kvm: kvm headers update Michael S. Tsirkin
2009-10-05 15:38 ` Avi Kivity
2009-10-05 19:27 ` Michael S. Tsirkin
2009-10-06 9:51 ` Avi Kivity
2009-10-06 9:52 ` Avi Kivity
2009-10-06 17:18 ` Michael S. Tsirkin
[not found] ` <200910061909.29977.arnd@arndb.de>
2009-10-08 13:39 ` Avi Kivity [this message]
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=4ACDEBAC.10200@redhat.com \
--to=avi@redhat.com \
--cc=arnd@arndb.de \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.