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
114 The PCI device backend driver allows the kernel to export arbitrary
115 PCI devices to other guests. If you select this to be a module, you
116 will need to make sure no other driver has bound to the device(s)
117 you want to make visible to other guests.
119 The parameter "passthrough" allows you specify how you want the PCI
120 devices to appear in the guest. You can choose the default (0) where
121 PCI topology starts at 00.00.0, or (1) for passthrough if you want
122 the PCI devices topology appear the same as in the host.
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)