public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL -tip v3] fix 39 'make headers_check' warnings
Date: Mon, 19 Jan 2009 13:53:16 +0200	[thread overview]
Message-ID: <497469AC.2030107@redhat.com> (raw)
In-Reply-To: <20090119110153.GA8321@uranus.ravnborg.org>

Sam Ravnborg wrote:
>> They are.  This bits advertise to userspace what features kvm supports, 
>> both compile- and run-time.
>>     
>
> This is wrong...
> The headers does not change with the kernel configuration and advertising the
> kvm features via a .h file like this is simply plain broken.
>   

Ok.  Don't know why I thought unifdef was supplied with the full 
configuration.

> You cannot assume that the header files are generated with the exact same config
> as used by the running kernel.
>   

This is just for arch specific defines.  I'll move these to asm/kvm.h.

> And userspace has in no way access to the CONFIG_ namespace which is purely kernel-internal.
>
> I cannot see how you have ever seen kcm advertise that for example KVM_CAP_USER_NMI
> equals to 22 because CONFIG_X86 is never (supposed to be) defined in userspace -
> except if you did so yourself by some means.
>   

We did, we ship a hacked-up kvm.h (generated by unifdef) with our userspace.

Thanks for the clarifications, helpful as always.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-01-19 11:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:04 [GIT PULL -tip v3] fix 39 'make headers_check' warnings Jaswinder Singh Rajput
2009-01-18 17:28 ` Ingo Molnar
2009-01-18 18:50   ` Ingo Molnar
2009-01-18 18:52     ` Ingo Molnar
2009-01-18 19:08     ` Sam Ravnborg
2009-01-18 19:09       ` Ingo Molnar
2009-01-18 19:45         ` Sam Ravnborg
2009-01-19  2:16       ` Jaswinder Singh Rajput
2009-01-19  5:27         ` Sam Ravnborg
2009-01-19  2:10     ` Jaswinder Singh Rajput
2009-01-19  2:20       ` Harvey Harrison
2009-01-19 11:15         ` Ingo Molnar
2009-01-19 18:08           ` Harvey Harrison
2009-01-18 18:56 ` Ingo Molnar
2009-01-19  9:19   ` Avi Kivity
2009-01-19 11:01     ` Sam Ravnborg
2009-01-19 11:53       ` Avi Kivity [this message]
2009-01-24  6:16         ` Jaswinder Singh Rajput
2009-02-04 14:28           ` Avi Kivity
2009-02-04 15:17             ` Jaswinder Singh Rajput
2009-02-04 15:40               ` Avi Kivity
2009-02-04 16:00                 ` Jaswinder Singh Rajput
2009-02-04 16:37                   ` Arnd Bergmann
2009-02-04 17:22                     ` Avi Kivity

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=497469AC.2030107@redhat.com \
    --to=avi@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=x86@kernel.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