aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/xen/Kconfig
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-07-11 16:49:41 -0400
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-07-19 21:04:20 -0400
commit2ebdc4263022e0015341016b123fe7f44f9cf396 (patch)
tree098f12c4ebfcb7a87b409255e50997e484ca1b59 /drivers/xen/Kconfig
parent778999703db6d875c22e1a8d02c8296ad4648958 (diff)
xen/pciback: Have 'passthrough' option instead of XEN_PCIDEV_BACKEND_PASS and XEN_PCIDEV_BACKEND_VPCI
.. compile options. This way the user can decide during runtime whether they want the default 'vpci' (virtual pci passthrough) or where the PCI devices are passed in without any BDF renumbering. The option 'passthrough' allows the user to toggle the it from 0 (vpci) to 1 (passthrough). Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'drivers/xen/Kconfig')
-rw-r--r--drivers/xen/Kconfig32
1 files changed, 10 insertions, 22 deletions
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index 0b6989f92041..9b700b4a987a 100644
--- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -109,34 +109,22 @@ config XEN_PCIDEV_BACKEND
109 tristate "Xen PCI-device backend driver" 109 tristate "Xen PCI-device backend driver"
110 depends on PCI && X86 && XEN 110 depends on PCI && X86 && XEN
111 depends on XEN_BACKEND 111 depends on XEN_BACKEND
112 default m
112 help 113 help
113 The PCI device backend driver allows the kernel to export arbitrary 114 The PCI device backend driver allows the kernel to export arbitrary
114 PCI devices to other guests. If you select this to be a module, you 115 PCI devices to other guests. If you select this to be a module, you
115 will need to make sure no other driver has bound to the device(s) 116 will need to make sure no other driver has bound to the device(s)
116 you want to make visible to other guests. 117 you want to make visible to other guests.
117 118
118choice 119 The parameter "passthrough" allows you specify how you want the PCI
119 prompt "PCI Backend Mode" 120 devices to appear in the guest. You can choose the default (0) where
120 depends on XEN_PCIDEV_BACKEND 121 PCI topology starts at 00.00.0, or (1) for passthrough if you want
121 122 the PCI devices topology appear the same as in the host.
122config XEN_PCIDEV_BACKEND_VPCI
123 bool "Virtual PCI"
124 help
125 This PCI Backend hides the true PCI topology and makes the frontend
126 think there is a single PCI bus with only the exported devices on it.
127 For example, a device at 03:05.0 will be re-assigned to 00:00.0. A
128 second device at 02:1a.1 will be re-assigned to 00:01.1.
129
130config XEN_PCIDEV_BACKEND_PASS
131 bool "Passthrough"
132 help
133 This PCI Backend provides a real view of the PCI topology to the
134 frontend (for example, a device at 06:01.b will still appear at
135 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed
136 PCI devices to its driver domains. This may be required for drivers
137 which depend on finding their hardward in certain bus/slot
138 locations.
139 123
140endchoice 124 The "hide" parameter (only applicable if backend driver is compiled
125 into the kernel) allows you to bind the PCI devices to this module
126 from the default device drivers. The argument is the list of PCI BDFs:
127 xen-pciback.hide=(03:00.0)(04:00.0)
141 128
129 If in doubt, say m.
142endmenu 130endmenu