From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm-29 and linux 2.6.22.1-cfs-v19
Date: Sat, 14 Jul 2007 15:13:15 -0500 [thread overview]
Message-ID: <46992E5B.1030102@codemonkey.ws> (raw)
In-Reply-To: <200707141956.41423.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Chris Clayton wrote:
> Hi,
>
> I'm building kvm-29 on a system that is running linux-2.6.22.1-cfs-v19. When
> the modules are built I get warnings about set_64bit:
>
> CC [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/vmx-debug.o
> CC [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm_main.o
> CC [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/mmu.o
> /home/users/chris/rpm/BUILD/kvm-29/kernel/mmu.c: In function 'set_shadow_pte':
> /home/users/chris/rpm/BUILD/kvm-29/kernel/mmu.c:202: warning: implicit
> declaration of function 'set_64bit'
> CC [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/x86_emulate.o
> CC [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/anon_inodes.o
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm.o
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-intel.o
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-amd.o
> Building modules, stage 2.
> MODPOST 3 modules
> WARNING: "set_64bit" [/home/users/chris/rpm/BUILD/kvm-29/kernel/kvm.ko]
> undefined!
> CC /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-amd.mod.o
> CC /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-intel.mod.o
> CC /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm.mod.o
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-amd.ko
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm-intel.ko
> LD [M] /home/users/chris/rpm/BUILD/kvm-29/kernel/kvm.ko
> m
> Because set_64bit is undefined, kvm.ko (and kvm-intel.ko) can't be loaded.
>
> I've found the set_64bit in the kernel sources - it's a macro in
> asm-i386/cmpxchg.h. The problem is that the macro(and some realted macros and
> definitions are guarded by "#ifdef CONFIG_X86_CMPXCHG64". Since that isn't
> defined for my kernel, set_64bit is not defined either.
>
KVM depends on CONFIG_X86_CMPXCHG64 which also depends on CONFIG_X86_PAE.
Regards,
Anthony Liguori
> If I comment the guarding #ifdef (and its partner #endif) kvm builds fine and
> everything seems to work OK.- the modules load and Damn Small Linux and
> FreeBSD run fine.
>
> Any advice would be much appreciated and more than happy to test patches.
>
> I'm not subscribed, so please cc me.
>
> Thanks
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-14 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 19:56 kvm-29 and linux 2.6.22.1-cfs-v19 Chris Clayton
[not found] ` <200707141956.41423.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-07-14 20:13 ` Anthony Liguori [this message]
[not found] ` <46992E5B.1030102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-07-14 20:58 ` Chris Clayton
[not found] ` <200707142058.27525.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-07-14 23:09 ` Anthony Liguori
[not found] ` <469957A8.9030402-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-07-15 6:17 ` 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=46992E5B.1030102@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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