From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Andrew Morton wrote:
> On Thu, 09 Aug 2007 01:48:07 +0300
> Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> * Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent 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
[not found] ` <20070808151446.9a4eebda.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-08-08 22:19 ` Ingo Molnar
[not found] ` <20070808221956.GA16238-X9Un+BFzKDI@public.gmane.org>
2007-08-08 22:48 ` Avi Kivity
[not found] ` <46BA4827.3080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-08 22:59 ` Andrew Morton
[not found] ` <20070808155901.bcb249d9.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-08-08 23:09 ` Avi Kivity [this message]
[not found] ` <46BA4D12.8090301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-13 17:31 ` Satyam Sharma
[not found] ` <a781481a0708131031k7e2bcc18t3fd0e7709e14d4a2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-13 17:37 ` Luck, Tony
[not found] ` <617E1C2C70743745A92448908E030B2A0224CFEF-1a9uaKK1+wKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
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-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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