[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Minor bugs in latest code drop


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • From: "barry" <barry@xxxxxxxxx>
  • Date: Mon, 5 Apr 2004 10:45:41 -0400
  • Delivery-date: Mon, 05 Apr 2004 15:34:50 +0100
  • Importance: Normal
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>

I have a couple of minor bugs in the latest code (with nodev=y).

 

1)       The arch/i386/Rules.mk specifies –Werror -, and a few modules have warnings (might be my gcc version [3.3.2]…). E.G.

gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -O3 -iwithprefix include -Wall -DMONITOR_BASE=0xFC500000 -fomit-frame-pointer -I/home/barry/xen/xen/include -D__KERNEL__ -Wno-pointer-arith -Wredundant-decls -m32 -march=i686 -DNDEBUG -DNO_DEVICES_IN_XEN -c schedule.c -o schedule.o

schedule.c:666: warning: `process_timeout' defined but not used”

 

I fixed the problem by removing –Werror from Rules.mk

 

      2)  in setup.c – with nodev=y, in my environment I have no modules that have any __init code in them. The do_initcalls routine doesn’t work properly in this case, and tries to call the first one before checking that there are no more… I fixed the problem by moving the do_initcalls into the conditional code for handling devices. I am not sure why you are not seeing the same problem.

 

 


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.