The latter is easily fixed - by the developer compiling the module with -DDEBUG. And during runtime - the loglvl provides quite a lot of useful data. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
@@ -139,13 +139,4 @@ config XEN_PCIDEV_BACKEND_PASS
endchoice
-config XEN_PCIDEV_BE_DEBUG
- bool "Xen PCI Backend Debugging"
- depends on XEN_PCIDEV_BACKEND
- default n
- help
- Allows to observe all of the traffic from the frontend/backend
- when reading and writting to the configuration registers.
- If in doubt, say no.
-
endmenu
@@ -6,7 +6,3 @@ xen-pciback-y += conf_space.o conf_space_header.o \
conf_space_quirks.o
xen-pciback-$(CONFIG_XEN_PCIDEV_BACKEND_VPCI) += vpci.o
xen-pciback-$(CONFIG_XEN_PCIDEV_BACKEND_PASS) += passthrough.o
-ifeq ($(CONFIG_XEN_PCIDEV_BE_DEBUG),y)
-EXTRA_CFLAGS += -DDEBUG
-endif