From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Sheng Yang <yasker@gmail.com>, KVM list <kvm@vger.kernel.org>,
Andrea Arcangeli <andrea@qumranet.com>
Subject: Re: Build failure w/o mmu notifiers
Date: Sun, 19 Oct 2008 10:57:24 +0200 [thread overview]
Message-ID: <48FAF674.7060604@redhat.com> (raw)
In-Reply-To: <6A5EF471-A7FF-4B50-9F9E-70272D6F9A04@suse.de>
Alexander Graf wrote:
>
> On 18.10.2008, at 12:51, Avi Kivity wrote:
>
>> Alexander Graf wrote:
>>>
>>> So if I don't select kvm in the kernel (either as module or compiled
>>> in) I can't build an external module providing kvm's functionality?
>>> That doesn't seem really useful to me...
>>>
>>
>> The external module hackball should detect that you don't have
>> CONFIG_MMU_NOTIFIERS set and supply some compatibility glue. What
>> error are you seeing?
>
> Basically struct mmu_notifier is not found, but requested by the code:
>
> rm -f include/asm include-compat/asm
> ln -sf asm-x86 include/asm
> ln -sf asm-x86 include-compat/asm
> make -C /usr/src/linux-obj/i586/default M=`pwd` \
> LINUXINCLUDE="-I`pwd`/include -Iinclude \
> -Iinclude2 -I/lib/modules/2.6.27.1-2-default/source/include \
> -Iarch/x86/include -I`pwd`/include-compat \
> -include include/linux/autoconf.h \
> -include `pwd`/x86/external-module-compat.h "
> make[1]: Entering directory `/usr/src/linux-2.6.27.1-2-obj/i386/default'
> make -C ../../../linux-2.6.27.1-2
> O=/usr/src/linux-2.6.27.1-2-obj/i386/default/.
> LD
> /usr/src/packages/BUILD/kvm-77/suse-kernel/default/x86/built-in.o
> CC [M] /usr/src/packages/BUILD/kvm-77/suse-kernel/default/x86/svm.o
> In file included from
> /usr/src/packages/BUILD/kvm-77/suse-kernel/default/x86/svm.c:16:
> /usr/src/packages/BUILD/kvm-77/suse-kernel/default/include/linux/kvm_host.h:128:
> error: field 'mmu_notifier' has incomplete type
> make[5]: ***
> [/usr/src/packages/BUILD/kvm-77/suse-kernel/default/x86/svm.o] Error 1
> make[4]: *** [/usr/src/packages/BUILD/kvm-77/suse-kernel/default/x86]
> Error 2
> make[3]: ***
> [_module_/usr/src/packages/BUILD/kvm-77/suse-kernel/default] Error 2
> make[2]: *** [sub-make] Error 2
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.27.1-2-obj/i386/default'
> make: *** [all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.20019 (%build)
>
> When I remove the struct references it breaks later on due to
> missing(?) inline functions.
>
Yes, there is an alternate definition in
kernel/include-compat/linux/mmu_notifier.h, but it doesn't get included
since the host's mmu_notifier.h has priority; and the host doesn't
define the structure if !CONFIG_MMU_NOTIFIERS.
I recommend configuring the host with KVM and throwing the modules away
if you want the external module. You'll get better functionality so
it's worth the minor hassle.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-19 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 16:34 Build failure w/o mmu notifiers Alexander Graf
2008-10-17 17:25 ` Sheng Yang
2008-10-17 17:47 ` Alexander Graf
2008-10-17 18:17 ` Sheng Yang
2008-10-17 18:36 ` Alexander Graf
2008-10-17 19:25 ` Andrea Arcangeli
2008-10-18 10:51 ` Avi Kivity
2008-10-18 11:12 ` Alexander Graf
2008-10-19 8:57 ` Avi Kivity [this message]
2008-10-18 7:21 ` Nikola Ciprich
2008-10-18 10:52 ` 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=48FAF674.7060604@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=andrea@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=yasker@gmail.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.