public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kvm warning
Date: Thu, 09 Aug 2007 02:09:06 +0300	[thread overview]
Message-ID: <46BA4D12.8090301@qumranet.com> (raw)
In-Reply-To: <20070808155901.bcb249d9.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Thu, 09 Aug 2007 01:48:07 +0300
> Avi Kivity <avi@qumranet.com> wrote:
>
>   
>> Ingo Molnar wrote:
>>     
>>> * Andrew Morton <akpm@linux-foundation.org> wrote:
>>>
>>>   
>>>       
>>>> ia64 allmodconfig says
>>>>
>>>> drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' 
>>>> refers to undefined symbol 'PREEMPT_NOTIFIERS'
>>>>     
>>>>         
>>> hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other 
>>> arches? Due to that ia64 also misses out on voluntary preempt and on 
>>> preempt-bkl.
>>>
>>>   
>>>       
>> Even more hm, how does ia64 manage to enable kvm?  It 'depends on X86' 
>> at this moment.
>>
>>     
>
> beats me.  CONFIG_KVM doesn't get set.  But it seems that kconfig wants
> to do error-checking on that item anyway.
>
>
>   

I could do a 'select PREEMPT_NOTIFIERS if X86' but it seems silly.  I'd 
call it a Kconfig bug.




  reply	other threads:[~2007-08-08 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 22:14 kvm warning Andrew Morton
2007-08-08 22:19 ` Ingo Molnar
2007-08-08 22:48   ` Avi Kivity
2007-08-08 22:59     ` Andrew Morton
2007-08-08 23:09       ` Avi Kivity [this message]
2007-08-13 17:31         ` Satyam Sharma
2007-08-13 17:37           ` Luck, Tony
2007-08-13 18:11             ` Satyam Sharma

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=46BA4D12.8090301@qumranet.com \
    --to=avi@qumranet.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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