[Xen-devel] Compilation problems: oldstyle/xenlinux 2.6.38, blktap2

[Alex Bligh <alex@xxxxxxxxxxx>]

I am trying to port Andrew Lyon's oldstyle/xenlinux patches against
2.6.38 to an Ubuntu 2.6.38 Natty kernel.

I am running across this problem, which is in essence that the same
functions are implemented in blktap2 and blktap2-new:

 LD      drivers/xen/built-in.o
drivers/xen/blktap2-new/built-in.o: In function `blktap_ring_init':
/home/amb/xen/ubuntu/git/ubuntu-natty/drivers/xen/blktap2-new/ring.c:521: 
multiple definition of `blktap_ring_init'
drivers/xen/blktap2/built-in.o:/home/amb/xen/ubuntu/git/ubuntu-natty/drivers/xen/blktap2/ring.c:587: 
first defined here
drivers/xen/blktap2-new/built-in.o: In function `blktap_ring_destroy':
/home/amb/xen/ubuntu/git/ubuntu-natty/drivers/xen/blktap2-new/ring.c:459: 
multiple definition of `blktap_ring_destroy'
drivers/xen/blktap2/built-in.o:/home/amb/xen/ubuntu/git/ubuntu-natty/drivers/xen/blktap2/ring.c:557: 
first defined here
drivers/xen/blktap2-new/built-in.o: In function `blktap_device_init':
/home/amb/xen/ubuntu/git/ubuntu-natty/drivers/xen/blktap2-new/device.c:550:
...
[similar snipped]
...
make[2]: *** [drivers/xen/built-in.o] Error 1
make[1]: *** [drivers/xen] Error 2
make: *** [drivers] Error 2


As far as I can tell from the Makefile, both directories are always built:

 obj-$(CONFIG_XEN_BLKDEV_TAP2)           += blktap2/ blktap2-new/

What's the difference between blktap2 and blktap2-new? Should only
one be built? I can't see a config option that switches between them.

I know one option is to just build blktap instead and ignore blktap2.
If I want to run this as a dom0 for Xen 3.3, will I lose anything
by not having blktap2?

--
Alex Bligh


CONFIG_X86_XEN_MCE=y
CONFIG_XEN_PCIDEV_FRONTEND=y
# CONFIG_XEN_PCIDEV_FE_DEBUG is not set
CONFIG_NETXEN_NIC=m
# CONFIG_TCG_XEN is not set
# CONFIG_XEN_WDT is not set
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030207
# XEN
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_DOMCTL=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKDEV_TAP2=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_NETDEV_TX_SHIFT=8
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_NETDEV_LOOPBACK is not set
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_SCSI_BACKEND=m
CONFIG_XEN_USB_BACKEND=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m
CONFIG_XEN_SCSI_FRONTEND=m
CONFIG_XEN_USB_FRONTEND=m
CONFIG_XEN_USB_FRONTEND_HCD_STATS=y
# CONFIG_XEN_USB_FRONTEND_HCD_PM is not set
CONFIG_XEN_GRANT_DEV=y
CONFIG_XEN_FRAMEBUFFER=y
CONFIG_XEN_KEYBOARD=y
CONFIG_XEN_DISABLE_SERIAL=y
CONFIG_XEN_SYSFS=y
CONFIG_XEN_NR_GUEST_DEVICES=256
CONFIG_XEN_COMPAT_030002_AND_LATER=y
# CONFIG_XEN_COMPAT_030004_AND_LATER is not set
# CONFIG_XEN_COMPAT_030100_AND_LATER is not set
# CONFIG_XEN_COMPAT_030200_AND_LATER is not set
# CONFIG_XEN_COMPAT_030300_AND_LATER is not set
# CONFIG_XEN_COMPAT_030400_AND_LATER is not set
# CONFIG_XEN_COMPAT_040000_AND_LATER is not set
# CONFIG_XEN_COMPAT_040100_AND_LATER is not set
# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
CONFIG_XEN_COMPAT=0x030002
CONFIG_XEN_SMPBOOT=y
CONFIG_XEN_DEVMEM=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel