From: Andrew Morton <akpm@linux-foundation.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kvm warning
Date: Wed, 8 Aug 2007 15:59:01 -0700 [thread overview]
Message-ID: <20070808155901.bcb249d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <46BA4827.3080907@qumranet.com>
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.
btw, testing of Kconfig can be done for any architecture without
installation of a toolchain for that architecture. Set $ARCH and run
mrproper then use menuconfig/oldconfig/allmodconfig/allconfig as usual.
Judging by the number of Kconfig problem I see, this is a big secret ;)
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: kvm warning
Date: Wed, 8 Aug 2007 15:59:01 -0700 [thread overview]
Message-ID: <20070808155901.bcb249d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <46BA4827.3080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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.
btw, testing of Kconfig can be done for any architecture without
installation of a toolchain for that architecture. Set $ARCH and run
mrproper then use menuconfig/oldconfig/allmodconfig/allconfig as usual.
Judging by the number of Kconfig problem I see, this is a big secret ;)
-------------------------------------------------------------------------
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:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:14 kvm warning Andrew Morton
2007-08-08 22:14 ` Andrew Morton
2007-08-08 22:19 ` Ingo Molnar
2007-08-08 22:19 ` Ingo Molnar
2007-08-08 22:48 ` Avi Kivity
2007-08-08 22:48 ` Avi Kivity
2007-08-08 22:59 ` Andrew Morton [this message]
2007-08-08 22:59 ` Andrew Morton
2007-08-08 23:09 ` Avi Kivity
2007-08-08 23:09 ` Avi Kivity
2007-08-13 17:31 ` Satyam Sharma
2007-08-13 17:31 ` Satyam Sharma
2007-08-13 17:37 ` Luck, Tony
2007-08-13 17:37 ` Luck, Tony
2007-08-13 18:11 ` Satyam Sharma
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=20070808155901.bcb249d9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--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 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.