1 menu "Xen driver support"
5 bool "Xen memory balloon driver"
8 The balloon driver allows the Xen domain to request more memory from
9 the system to expand the domain's memory allocation, or alternatively
10 return unneeded memory to the system.
12 config XEN_SCRUB_PAGES
13 bool "Scrub pages before returning them to system"
14 depends on XEN_BALLOON
17 Scrub pages before returning them to the system for reuse by
18 other domains. This makes sure that any confidential data
19 is not accidentally visible to other domains. Is it more
20 secure, but slightly less efficient.
24 tristate "Xen /dev/xen/evtchn device"
27 The evtchn driver allows a userspace process to triger event
28 channels and to receive notification of an event channel
33 bool "Backend driver support"
37 Support for backend device drivers that provide I/O services
38 to other virtual machines.
41 tristate "Xen filesystem"
44 The xen filesystem provides a way for domains to share
45 information with each other and with the hypervisor.
46 For example, by reading and writing the "xenbus" file, guests
47 may pass arbitrary information to the initial domain.
50 config XEN_COMPAT_XENFS
51 bool "Create compatibility mount point /proc/xen"
55 The old xenstore userspace tools expect to find "xenbus"
56 under /proc/xen, but "xenbus" is now found at the root of the
57 xenfs filesystem. Selecting this causes the kernel to create
58 the compatibility mount point /proc/xen if it is running on
62 config XEN_SYS_HYPERVISOR
63 bool "Create xen entries under /sys/hypervisor"
68 Create entries under /sys/hypervisor describing the Xen
69 hypervisor environment. When running native or in another
70 virtual environment, /sys/hypervisor will still be present,
71 but will have no xen contents.
73 config XEN_XENBUS_FRONTEND
77 tristate "userspace grant access device driver"
82 Allows userspace processes to use grants.
84 config XEN_GRANT_DEV_ALLOC
85 tristate "User-space grant reference allocator driver"
89 Allows userspace processes to create pages with access granted
90 to other domains. This can be used to implement frontend drivers
91 or as part of an inter-domain shared memory channel.
93 config XEN_PLATFORM_PCI
94 tristate "xen platform pci device driver"
95 depends on XEN_PVHVM && PCI
98 Driver for the Xen PCI Platform device: it is responsible for
99 initializing xenbus and grant_table when running in a Xen HVM
100 domain. As a consequence this driver is required to run any Xen PV
108 config XEN_PCIDEV_BACKEND
109 tristate "Xen PCI-device backend driver"
110 depends on PCI && X86 && XEN
111 depends on XEN_BACKEND
113 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 will need to make sure no other driver has bound to the device(s)
116 you want to make visible to other guests.
119 prompt "PCI Backend Mode"
120 depends on XEN_PCIDEV_BACKEND
122 config XEN_PCIDEV_BACKEND_VPCI
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.
130 config XEN_PCIDEV_BACKEND_PASS
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
142 config XEN_PCIDEV_BE_DEBUG
143 bool "Xen PCI Backend Debugging"
144 depends on XEN_PCIDEV_BACKEND
147 Allows to observe all of the traffic from the frontend/backend
148 when reading and writting to the configuration registers.