ia64/xen-unstable

changeset 9207:80bc37d5a32f

Explain disadvantages of building pciback as a module in Kconfig help.
Fix a module-loading bug in pciback.

From: Jan Beulich
Signed-off-by: Keir Fraser <keir@xensource.com>
author kaf24@firebug.cl.cam.ac.uk
date Thu Mar 09 15:56:12 2006 +0100 (2006-03-09)
parents d4a2af362e5e
children c176d2e45117
files linux-2.6-xen-sparse/drivers/xen/Kconfig linux-2.6-xen-sparse/drivers/xen/pciback/pci_stub.c
line diff
     1.1 --- a/linux-2.6-xen-sparse/drivers/xen/Kconfig	Thu Mar 09 15:16:35 2006 +0100
     1.2 +++ b/linux-2.6-xen-sparse/drivers/xen/Kconfig	Thu Mar 09 15:56:12 2006 +0100
     1.3 @@ -35,7 +35,9 @@ config XEN_PCIDEV_BACKEND
     1.4  	default XEN_PRIVILEGED_GUEST
     1.5  	help
     1.6  	  The PCI device backend driver allows the kernel to export arbitrary
     1.7 -	  PCI devices to other guests.
     1.8 +	  PCI devices to other guests. If you select this to be a module, you
     1.9 +	  will need to make sure no other driver has bound to the device(s)
    1.10 +	  you want to make visible to other guests.
    1.11  
    1.12  choice
    1.13  	prompt "PCI Backend Mode"
     2.1 --- a/linux-2.6-xen-sparse/drivers/xen/pciback/pci_stub.c	Thu Mar 09 15:16:35 2006 +0100
     2.2 +++ b/linux-2.6-xen-sparse/drivers/xen/pciback/pci_stub.c	Thu Mar 09 15:56:12 2006 +0100
     2.3 @@ -378,7 +378,7 @@ fs_initcall(pcistub_init);
     2.4  
     2.5  static int __init pciback_init(void)
     2.6  {
     2.7 -#ifndef MODULE
     2.8 +#ifdef MODULE
     2.9  	int err;
    2.10  
    2.11  	err = pcistub_init();