public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: kvm-29 and linux 2.6.22.1-cfs-v19
Date: Sat, 14 Jul 2007 19:56:41 +0000	[thread overview]
Message-ID: <200707141956.41423.chris2553@googlemail.com> (raw)

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.

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/

             reply	other threads:[~2007-07-14 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-14 19:56 Chris Clayton [this message]
     [not found] ` <200707141956.41423.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-07-14 20:13   ` kvm-29 and linux 2.6.22.1-cfs-v19 Anthony Liguori
     [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=200707141956.41423.chris2553@googlemail.com \
    --to=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