2010-03-05 21:44:18 +00:00
|
|
|
menu "Xen driver support"
|
|
|
|
|
depends on XEN
|
|
|
|
|
|
2008-04-02 17:54:13 +00:00
|
|
|
config XEN_BALLOON
|
|
|
|
|
bool "Xen memory balloon driver"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The balloon driver allows the Xen domain to request more memory from
|
|
|
|
|
the system to expand the domain's memory allocation, or alternatively
|
|
|
|
|
return unneeded memory to the system.
|
|
|
|
|
|
2011-07-08 18:26:21 +00:00
|
|
|
config XEN_SELFBALLOONING
|
|
|
|
|
bool "Dynamically self-balloon kernel memory to target"
|
2011-07-30 15:21:09 +00:00
|
|
|
depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP && XEN_TMEM
|
2011-07-08 18:26:21 +00:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Self-ballooning dynamically balloons available kernel memory driven
|
|
|
|
|
by the current usage of anonymous memory ("committed AS") and
|
|
|
|
|
controlled by various sysfs-settable parameters. Configuring
|
|
|
|
|
FRONTSWAP is highly recommended; if it is not configured, self-
|
|
|
|
|
ballooning is disabled by default but can be enabled with the
|
|
|
|
|
'selfballooning' kernel boot parameter. If FRONTSWAP is configured,
|
|
|
|
|
frontswap-selfshrinking is enabled by default but can be disabled
|
|
|
|
|
with the 'noselfshrink' kernel boot parameter; and self-ballooning
|
|
|
|
|
is enabled by default but can be disabled with the 'noselfballooning'
|
|
|
|
|
kernel boot parameter. Note that systems without a sufficiently
|
|
|
|
|
large swap device should not enable self-ballooning.
|
2008-04-02 17:54:13 +00:00
|
|
|
|
2011-07-26 00:12:06 +00:00
|
|
|
config XEN_BALLOON_MEMORY_HOTPLUG
|
|
|
|
|
bool "Memory hotplug support for Xen balloon driver"
|
|
|
|
|
default n
|
|
|
|
|
depends on XEN_BALLOON && MEMORY_HOTPLUG
|
|
|
|
|
help
|
|
|
|
|
Memory hotplug support for Xen balloon driver allows expanding memory
|
|
|
|
|
available for the system above limit declared at system startup.
|
|
|
|
|
It is very useful on critical systems which require long
|
|
|
|
|
run without rebooting.
|
|
|
|
|
|
|
|
|
|
Memory could be hotplugged in following steps:
|
|
|
|
|
|
|
|
|
|
1) dom0: xl mem-max <domU> <maxmem>
|
|
|
|
|
where <maxmem> is >= requested memory size,
|
|
|
|
|
|
|
|
|
|
2) dom0: xl mem-set <domU> <memory>
|
|
|
|
|
where <memory> is requested memory size; alternatively memory
|
|
|
|
|
could be added by writing proper value to
|
|
|
|
|
/sys/devices/system/xen_memory/xen_memory0/target or
|
|
|
|
|
/sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
|
|
|
|
|
|
|
|
|
|
3) domU: for i in /sys/devices/system/memory/memory*/state; do \
|
|
|
|
|
[ "`cat "$i"`" = offline ] && echo online > "$i"; done
|
|
|
|
|
|
|
|
|
|
Memory could be onlined automatically on domU by adding following line to udev rules:
|
|
|
|
|
|
|
|
|
|
SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
|
|
|
|
|
|
|
|
|
|
In that case step 3 should be omitted.
|
|
|
|
|
|
2008-04-02 17:54:13 +00:00
|
|
|
config XEN_SCRUB_PAGES
|
|
|
|
|
bool "Scrub pages before returning them to system"
|
|
|
|
|
depends on XEN_BALLOON
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Scrub pages before returning them to the system for reuse by
|
|
|
|
|
other domains. This makes sure that any confidential data
|
|
|
|
|
is not accidentally visible to other domains. Is it more
|
|
|
|
|
secure, but slightly less efficient.
|
|
|
|
|
If in doubt, say yes.
|
2009-01-08 02:07:11 +00:00
|
|
|
|
2009-02-07 03:21:19 +00:00
|
|
|
config XEN_DEV_EVTCHN
|
|
|
|
|
tristate "Xen /dev/xen/evtchn device"
|
|
|
|
|
default y
|
|
|
|
|
help
|
2012-04-13 15:14:11 +00:00
|
|
|
The evtchn driver allows a userspace process to trigger event
|
2009-02-07 03:21:19 +00:00
|
|
|
channels and to receive notification of an event channel
|
|
|
|
|
firing.
|
|
|
|
|
If in doubt, say yes.
|
|
|
|
|
|
2009-02-09 20:05:51 +00:00
|
|
|
config XEN_BACKEND
|
2009-03-22 06:29:34 +00:00
|
|
|
bool "Backend driver support"
|
2009-02-09 20:05:51 +00:00
|
|
|
depends on XEN_DOM0
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Support for backend device drivers that provide I/O services
|
|
|
|
|
to other virtual machines.
|
|
|
|
|
|
2009-01-08 02:07:11 +00:00
|
|
|
config XENFS
|
|
|
|
|
tristate "Xen filesystem"
|
2011-12-16 16:34:33 +00:00
|
|
|
select XEN_PRIVCMD
|
2009-01-08 02:07:11 +00:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The xen filesystem provides a way for domains to share
|
|
|
|
|
information with each other and with the hypervisor.
|
|
|
|
|
For example, by reading and writing the "xenbus" file, guests
|
|
|
|
|
may pass arbitrary information to the initial domain.
|
|
|
|
|
If in doubt, say yes.
|
|
|
|
|
|
|
|
|
|
config XEN_COMPAT_XENFS
|
|
|
|
|
bool "Create compatibility mount point /proc/xen"
|
|
|
|
|
depends on XENFS
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The old xenstore userspace tools expect to find "xenbus"
|
|
|
|
|
under /proc/xen, but "xenbus" is now found at the root of the
|
|
|
|
|
xenfs filesystem. Selecting this causes the kernel to create
|
2009-01-26 10:12:25 +00:00
|
|
|
the compatibility mount point /proc/xen if it is running on
|
2009-01-08 02:07:11 +00:00
|
|
|
a xen platform.
|
|
|
|
|
If in doubt, say yes.
|
|
|
|
|
|
2009-03-10 21:39:59 +00:00
|
|
|
config XEN_SYS_HYPERVISOR
|
|
|
|
|
bool "Create xen entries under /sys/hypervisor"
|
2010-03-05 21:44:18 +00:00
|
|
|
depends on SYSFS
|
2009-03-10 21:39:59 +00:00
|
|
|
select SYS_HYPERVISOR
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Create entries under /sys/hypervisor describing the Xen
|
|
|
|
|
hypervisor environment. When running native or in another
|
|
|
|
|
virtual environment, /sys/hypervisor will still be present,
|
2010-03-05 21:44:18 +00:00
|
|
|
but will have no xen contents.
|
|
|
|
|
|
2009-02-09 20:05:51 +00:00
|
|
|
config XEN_XENBUS_FRONTEND
|
2011-01-14 02:46:48 +00:00
|
|
|
tristate
|
|
|
|
|
|
2010-12-14 18:40:46 +00:00
|
|
|
config XEN_GNTDEV
|
|
|
|
|
tristate "userspace grant access device driver"
|
|
|
|
|
depends on XEN
|
2011-02-10 12:08:21 +00:00
|
|
|
default m
|
2010-12-14 18:40:46 +00:00
|
|
|
select MMU_NOTIFIER
|
|
|
|
|
help
|
|
|
|
|
Allows userspace processes to use grants.
|
2010-12-10 14:39:15 +00:00
|
|
|
|
2011-02-07 22:23:05 +00:00
|
|
|
config XEN_GRANT_DEV_ALLOC
|
|
|
|
|
tristate "User-space grant reference allocator driver"
|
|
|
|
|
depends on XEN
|
2011-02-10 12:08:21 +00:00
|
|
|
default m
|
2011-02-07 22:23:05 +00:00
|
|
|
help
|
|
|
|
|
Allows userspace processes to create pages with access granted
|
|
|
|
|
to other domains. This can be used to implement frontend drivers
|
|
|
|
|
or as part of an inter-domain shared memory channel.
|
|
|
|
|
|
2010-05-11 14:05:49 +00:00
|
|
|
config SWIOTLB_XEN
|
|
|
|
|
def_bool y
|
2010-10-08 15:06:20 +00:00
|
|
|
depends on PCI
|
|
|
|
|
select SWIOTLB
|
2010-05-11 14:05:49 +00:00
|
|
|
|
2011-06-17 21:06:20 +00:00
|
|
|
config XEN_TMEM
|
|
|
|
|
bool
|
|
|
|
|
default y if (CLEANCACHE || FRONTSWAP)
|
|
|
|
|
help
|
|
|
|
|
Shim to interface in-kernel Transcendent Memory hooks
|
|
|
|
|
(e.g. cleancache and frontswap) to Xen tmem hypercalls.
|
|
|
|
|
|
xen/pciback: xen pci backend driver.
This is the host side counterpart to the frontend driver in
drivers/pci/xen-pcifront.c. The PV protocol is also implemented by
frontend drivers in other OSes too, such as the BSDs.
The PV protocol is rather simple. There is page shared with the guest,
which has the 'struct xen_pci_sharedinfo' embossed in it. The backend
has a thread that is kicked every-time the structure is changed and
based on the operation field it performs specific tasks:
XEN_PCI_OP_conf_[read|write]:
Read/Write 0xCF8/0xCFC filtered data. (conf_space*.c)
Based on which field is probed, we either enable/disable the PCI
device, change power state, read VPD, etc. The major goal of this
call is to provide a Physical IRQ (PIRQ) to the guest.
The PIRQ is Xen hypervisor global IRQ value irrespective of the IRQ
is tied in to the IO-APIC, or is a vector. For GSI type
interrupts, the PIRQ==GSI holds. For MSI/MSI-X the
PIRQ value != Linux IRQ number (thought PIRQ==vector).
Please note, that with Xen, all interrupts (except those level shared ones)
are injected directly to the guest - there is no host interaction.
XEN_PCI_OP_[enable|disable]_msi[|x] (pciback_ops.c)
Enables/disables the MSI/MSI-X capability of the device. These operations
setup the MSI/MSI-X vectors for the guest and pass them to the frontend.
When the device is activated, the interrupts are directly injected in the
guest without involving the host.
XEN_PCI_OP_aer_[detected|resume|mmio|slotreset]: In case of failure,
perform the appropriate AER commands on the guest. Right now that is
a cop-out - we just kill the guest.
Besides implementing those commands, it can also
- hide a PCI device from the host. When booting up, the user can specify
xen-pciback.hide=(1:0:0)(BDF..) so that host does not try to use the
device.
The driver was lifted from linux-2.6.18.hg tree and fixed up
so that it could compile under v3.0. Per suggestion from Jesse Barnes
moved the driver to drivers/xen/xen-pciback.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
2009-10-13 21:22:20 +00:00
|
|
|
config XEN_PCIDEV_BACKEND
|
|
|
|
|
tristate "Xen PCI-device backend driver"
|
|
|
|
|
depends on PCI && X86 && XEN
|
|
|
|
|
depends on XEN_BACKEND
|
2011-07-11 20:49:41 +00:00
|
|
|
default m
|
xen/pciback: xen pci backend driver.
This is the host side counterpart to the frontend driver in
drivers/pci/xen-pcifront.c. The PV protocol is also implemented by
frontend drivers in other OSes too, such as the BSDs.
The PV protocol is rather simple. There is page shared with the guest,
which has the 'struct xen_pci_sharedinfo' embossed in it. The backend
has a thread that is kicked every-time the structure is changed and
based on the operation field it performs specific tasks:
XEN_PCI_OP_conf_[read|write]:
Read/Write 0xCF8/0xCFC filtered data. (conf_space*.c)
Based on which field is probed, we either enable/disable the PCI
device, change power state, read VPD, etc. The major goal of this
call is to provide a Physical IRQ (PIRQ) to the guest.
The PIRQ is Xen hypervisor global IRQ value irrespective of the IRQ
is tied in to the IO-APIC, or is a vector. For GSI type
interrupts, the PIRQ==GSI holds. For MSI/MSI-X the
PIRQ value != Linux IRQ number (thought PIRQ==vector).
Please note, that with Xen, all interrupts (except those level shared ones)
are injected directly to the guest - there is no host interaction.
XEN_PCI_OP_[enable|disable]_msi[|x] (pciback_ops.c)
Enables/disables the MSI/MSI-X capability of the device. These operations
setup the MSI/MSI-X vectors for the guest and pass them to the frontend.
When the device is activated, the interrupts are directly injected in the
guest without involving the host.
XEN_PCI_OP_aer_[detected|resume|mmio|slotreset]: In case of failure,
perform the appropriate AER commands on the guest. Right now that is
a cop-out - we just kill the guest.
Besides implementing those commands, it can also
- hide a PCI device from the host. When booting up, the user can specify
xen-pciback.hide=(1:0:0)(BDF..) so that host does not try to use the
device.
The driver was lifted from linux-2.6.18.hg tree and fixed up
so that it could compile under v3.0. Per suggestion from Jesse Barnes
moved the driver to drivers/xen/xen-pciback.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
2009-10-13 21:22:20 +00:00
|
|
|
help
|
|
|
|
|
The PCI device backend driver allows the kernel to export arbitrary
|
|
|
|
|
PCI devices to other guests. If you select this to be a module, you
|
|
|
|
|
will need to make sure no other driver has bound to the device(s)
|
|
|
|
|
you want to make visible to other guests.
|
|
|
|
|
|
2011-07-11 20:49:41 +00:00
|
|
|
The parameter "passthrough" allows you specify how you want the PCI
|
|
|
|
|
devices to appear in the guest. You can choose the default (0) where
|
|
|
|
|
PCI topology starts at 00.00.0, or (1) for passthrough if you want
|
|
|
|
|
the PCI devices topology appear the same as in the host.
|
xen/pciback: xen pci backend driver.
This is the host side counterpart to the frontend driver in
drivers/pci/xen-pcifront.c. The PV protocol is also implemented by
frontend drivers in other OSes too, such as the BSDs.
The PV protocol is rather simple. There is page shared with the guest,
which has the 'struct xen_pci_sharedinfo' embossed in it. The backend
has a thread that is kicked every-time the structure is changed and
based on the operation field it performs specific tasks:
XEN_PCI_OP_conf_[read|write]:
Read/Write 0xCF8/0xCFC filtered data. (conf_space*.c)
Based on which field is probed, we either enable/disable the PCI
device, change power state, read VPD, etc. The major goal of this
call is to provide a Physical IRQ (PIRQ) to the guest.
The PIRQ is Xen hypervisor global IRQ value irrespective of the IRQ
is tied in to the IO-APIC, or is a vector. For GSI type
interrupts, the PIRQ==GSI holds. For MSI/MSI-X the
PIRQ value != Linux IRQ number (thought PIRQ==vector).
Please note, that with Xen, all interrupts (except those level shared ones)
are injected directly to the guest - there is no host interaction.
XEN_PCI_OP_[enable|disable]_msi[|x] (pciback_ops.c)
Enables/disables the MSI/MSI-X capability of the device. These operations
setup the MSI/MSI-X vectors for the guest and pass them to the frontend.
When the device is activated, the interrupts are directly injected in the
guest without involving the host.
XEN_PCI_OP_aer_[detected|resume|mmio|slotreset]: In case of failure,
perform the appropriate AER commands on the guest. Right now that is
a cop-out - we just kill the guest.
Besides implementing those commands, it can also
- hide a PCI device from the host. When booting up, the user can specify
xen-pciback.hide=(1:0:0)(BDF..) so that host does not try to use the
device.
The driver was lifted from linux-2.6.18.hg tree and fixed up
so that it could compile under v3.0. Per suggestion from Jesse Barnes
moved the driver to drivers/xen/xen-pciback.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
2009-10-13 21:22:20 +00:00
|
|
|
|
2011-07-11 20:49:41 +00:00
|
|
|
The "hide" parameter (only applicable if backend driver is compiled
|
|
|
|
|
into the kernel) allows you to bind the PCI devices to this module
|
|
|
|
|
from the default device drivers. The argument is the list of PCI BDFs:
|
|
|
|
|
xen-pciback.hide=(03:00.0)(04:00.0)
|
xen/pciback: xen pci backend driver.
This is the host side counterpart to the frontend driver in
drivers/pci/xen-pcifront.c. The PV protocol is also implemented by
frontend drivers in other OSes too, such as the BSDs.
The PV protocol is rather simple. There is page shared with the guest,
which has the 'struct xen_pci_sharedinfo' embossed in it. The backend
has a thread that is kicked every-time the structure is changed and
based on the operation field it performs specific tasks:
XEN_PCI_OP_conf_[read|write]:
Read/Write 0xCF8/0xCFC filtered data. (conf_space*.c)
Based on which field is probed, we either enable/disable the PCI
device, change power state, read VPD, etc. The major goal of this
call is to provide a Physical IRQ (PIRQ) to the guest.
The PIRQ is Xen hypervisor global IRQ value irrespective of the IRQ
is tied in to the IO-APIC, or is a vector. For GSI type
interrupts, the PIRQ==GSI holds. For MSI/MSI-X the
PIRQ value != Linux IRQ number (thought PIRQ==vector).
Please note, that with Xen, all interrupts (except those level shared ones)
are injected directly to the guest - there is no host interaction.
XEN_PCI_OP_[enable|disable]_msi[|x] (pciback_ops.c)
Enables/disables the MSI/MSI-X capability of the device. These operations
setup the MSI/MSI-X vectors for the guest and pass them to the frontend.
When the device is activated, the interrupts are directly injected in the
guest without involving the host.
XEN_PCI_OP_aer_[detected|resume|mmio|slotreset]: In case of failure,
perform the appropriate AER commands on the guest. Right now that is
a cop-out - we just kill the guest.
Besides implementing those commands, it can also
- hide a PCI device from the host. When booting up, the user can specify
xen-pciback.hide=(1:0:0)(BDF..) so that host does not try to use the
device.
The driver was lifted from linux-2.6.18.hg tree and fixed up
so that it could compile under v3.0. Per suggestion from Jesse Barnes
moved the driver to drivers/xen/xen-pciback.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
2009-10-13 21:22:20 +00:00
|
|
|
|
2011-07-11 20:49:41 +00:00
|
|
|
If in doubt, say m.
|
2011-12-16 16:34:33 +00:00
|
|
|
|
|
|
|
|
config XEN_PRIVCMD
|
|
|
|
|
tristate
|
|
|
|
|
depends on XEN
|
|
|
|
|
default m
|
|
|
|
|
|
xen/acpi-processor: C and P-state driver that uploads said data to hypervisor.
This driver solves three problems:
1). Parse and upload ACPI0007 (or PROCESSOR_TYPE) information to the
hypervisor - aka P-states (cpufreq data).
2). Upload the the Cx state information (cpuidle data).
3). Inhibit CPU frequency scaling drivers from loading.
The reason for wanting to solve 1) and 2) is such that the Xen hypervisor
is the only one that knows the CPU usage of different guests and can
make the proper decision of when to put CPUs and packages in proper states.
Unfortunately the hypervisor has no support to parse ACPI DSDT tables, hence it
needs help from the initial domain to provide this information. The reason
for 3) is that we do not want the initial domain to change P-states while the
hypervisor is doing it as well - it causes rather some funny cases of P-states
transitions.
For this to work, the driver parses the Power Management data and uploads said
information to the Xen hypervisor. It also calls acpi_processor_notify_smm()
to inhibit the other CPU frequency scaling drivers from being loaded.
Everything revolves around the 'struct acpi_processor' structure which
gets updated during the bootup cycle in different stages. At the startup, when
the ACPI parser starts, the C-state information is processed (processor_idle)
and saved in said structure as 'power' element. Later on, the CPU frequency
scaling driver (powernow-k8 or acpi_cpufreq), would call the the
acpi_processor_* (processor_perflib functions) to parse P-states information
and populate in the said structure the 'performance' element.
Since we do not want the CPU frequency scaling drivers from loading
we have to call the acpi_processor_* functions to parse the P-states and
call "acpi_processor_notify_smm" to stop them from loading.
There is also one oddity in this driver which is that under Xen, the
physical online CPU count can be different from the virtual online CPU count.
Meaning that the macros 'for_[online|possible]_cpu' would process only
up to virtual online CPU count. We on the other hand want to process
the full amount of physical CPUs. For that, the driver checks if the ACPI IDs
count is different from the APIC ID count - which can happen if the user
choose to use dom0_max_vcpu argument. In such a case a backup of the PM
structure is used and uploaded to the hypervisor.
[v1-v2: Initial RFC implementations that were posted]
[v3: Changed the name to passthru suggested by Pasi Kärkkäinen <pasik@iki.fi>]
[v4: Added vCPU != pCPU support - aka dom0_max_vcpus support]
[v5: Cleaned up the driver, fix bug under Athlon XP]
[v6: Changed the driver to a CPU frequency governor]
[v7: Jan Beulich <jbeulich@suse.com> suggestion to make it a cpufreq scaling driver
made me rework it as driver that inhibits cpufreq scaling driver]
[v8: Per Jan's review comments, fixed up the driver]
[v9: Allow to continue even if acpi_processor_preregister_perf.. fails]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
2012-02-03 21:03:20 +00:00
|
|
|
config XEN_ACPI_PROCESSOR
|
|
|
|
|
tristate "Xen ACPI processor"
|
2012-03-24 13:18:57 +00:00
|
|
|
depends on XEN && X86 && ACPI_PROCESSOR && CPU_FREQ
|
2012-03-13 17:28:12 +00:00
|
|
|
default m
|
xen/acpi-processor: C and P-state driver that uploads said data to hypervisor.
This driver solves three problems:
1). Parse and upload ACPI0007 (or PROCESSOR_TYPE) information to the
hypervisor - aka P-states (cpufreq data).
2). Upload the the Cx state information (cpuidle data).
3). Inhibit CPU frequency scaling drivers from loading.
The reason for wanting to solve 1) and 2) is such that the Xen hypervisor
is the only one that knows the CPU usage of different guests and can
make the proper decision of when to put CPUs and packages in proper states.
Unfortunately the hypervisor has no support to parse ACPI DSDT tables, hence it
needs help from the initial domain to provide this information. The reason
for 3) is that we do not want the initial domain to change P-states while the
hypervisor is doing it as well - it causes rather some funny cases of P-states
transitions.
For this to work, the driver parses the Power Management data and uploads said
information to the Xen hypervisor. It also calls acpi_processor_notify_smm()
to inhibit the other CPU frequency scaling drivers from being loaded.
Everything revolves around the 'struct acpi_processor' structure which
gets updated during the bootup cycle in different stages. At the startup, when
the ACPI parser starts, the C-state information is processed (processor_idle)
and saved in said structure as 'power' element. Later on, the CPU frequency
scaling driver (powernow-k8 or acpi_cpufreq), would call the the
acpi_processor_* (processor_perflib functions) to parse P-states information
and populate in the said structure the 'performance' element.
Since we do not want the CPU frequency scaling drivers from loading
we have to call the acpi_processor_* functions to parse the P-states and
call "acpi_processor_notify_smm" to stop them from loading.
There is also one oddity in this driver which is that under Xen, the
physical online CPU count can be different from the virtual online CPU count.
Meaning that the macros 'for_[online|possible]_cpu' would process only
up to virtual online CPU count. We on the other hand want to process
the full amount of physical CPUs. For that, the driver checks if the ACPI IDs
count is different from the APIC ID count - which can happen if the user
choose to use dom0_max_vcpu argument. In such a case a backup of the PM
structure is used and uploaded to the hypervisor.
[v1-v2: Initial RFC implementations that were posted]
[v3: Changed the name to passthru suggested by Pasi Kärkkäinen <pasik@iki.fi>]
[v4: Added vCPU != pCPU support - aka dom0_max_vcpus support]
[v5: Cleaned up the driver, fix bug under Athlon XP]
[v6: Changed the driver to a CPU frequency governor]
[v7: Jan Beulich <jbeulich@suse.com> suggestion to make it a cpufreq scaling driver
made me rework it as driver that inhibits cpufreq scaling driver]
[v8: Per Jan's review comments, fixed up the driver]
[v9: Allow to continue even if acpi_processor_preregister_perf.. fails]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
2012-02-03 21:03:20 +00:00
|
|
|
help
|
2012-05-04 21:04:12 +00:00
|
|
|
This ACPI processor uploads Power Management information to the Xen
|
|
|
|
|
hypervisor.
|
|
|
|
|
|
|
|
|
|
To do that the driver parses the Power Management data and uploads
|
|
|
|
|
said information to the Xen hypervisor. Then the Xen hypervisor can
|
|
|
|
|
select the proper Cx and Pxx states. It also registers itslef as the
|
|
|
|
|
SMM so that other drivers (such as ACPI cpufreq scaling driver) will
|
|
|
|
|
not load.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called xen_acpi_processor If you do not know what to choose, select
|
|
|
|
|
M here. If the CPUFREQ drivers are built in, select Y here.
|
xen/acpi-processor: C and P-state driver that uploads said data to hypervisor.
This driver solves three problems:
1). Parse and upload ACPI0007 (or PROCESSOR_TYPE) information to the
hypervisor - aka P-states (cpufreq data).
2). Upload the the Cx state information (cpuidle data).
3). Inhibit CPU frequency scaling drivers from loading.
The reason for wanting to solve 1) and 2) is such that the Xen hypervisor
is the only one that knows the CPU usage of different guests and can
make the proper decision of when to put CPUs and packages in proper states.
Unfortunately the hypervisor has no support to parse ACPI DSDT tables, hence it
needs help from the initial domain to provide this information. The reason
for 3) is that we do not want the initial domain to change P-states while the
hypervisor is doing it as well - it causes rather some funny cases of P-states
transitions.
For this to work, the driver parses the Power Management data and uploads said
information to the Xen hypervisor. It also calls acpi_processor_notify_smm()
to inhibit the other CPU frequency scaling drivers from being loaded.
Everything revolves around the 'struct acpi_processor' structure which
gets updated during the bootup cycle in different stages. At the startup, when
the ACPI parser starts, the C-state information is processed (processor_idle)
and saved in said structure as 'power' element. Later on, the CPU frequency
scaling driver (powernow-k8 or acpi_cpufreq), would call the the
acpi_processor_* (processor_perflib functions) to parse P-states information
and populate in the said structure the 'performance' element.
Since we do not want the CPU frequency scaling drivers from loading
we have to call the acpi_processor_* functions to parse the P-states and
call "acpi_processor_notify_smm" to stop them from loading.
There is also one oddity in this driver which is that under Xen, the
physical online CPU count can be different from the virtual online CPU count.
Meaning that the macros 'for_[online|possible]_cpu' would process only
up to virtual online CPU count. We on the other hand want to process
the full amount of physical CPUs. For that, the driver checks if the ACPI IDs
count is different from the APIC ID count - which can happen if the user
choose to use dom0_max_vcpu argument. In such a case a backup of the PM
structure is used and uploaded to the hypervisor.
[v1-v2: Initial RFC implementations that were posted]
[v3: Changed the name to passthru suggested by Pasi Kärkkäinen <pasik@iki.fi>]
[v4: Added vCPU != pCPU support - aka dom0_max_vcpus support]
[v5: Cleaned up the driver, fix bug under Athlon XP]
[v6: Changed the driver to a CPU frequency governor]
[v7: Jan Beulich <jbeulich@suse.com> suggestion to make it a cpufreq scaling driver
made me rework it as driver that inhibits cpufreq scaling driver]
[v8: Per Jan's review comments, fixed up the driver]
[v9: Allow to continue even if acpi_processor_preregister_perf.. fails]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
2012-02-03 21:03:20 +00:00
|
|
|
|
2012-06-07 11:56:51 +00:00
|
|
|
config XEN_MCE_LOG
|
|
|
|
|
bool "Xen platform mcelog"
|
|
|
|
|
depends on XEN_DOM0 && X86_64 && X86_MCE
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Allow kernel fetching MCE error from Xen platform and
|
|
|
|
|
converting it into Linux mcelog format for mcelog tools
|
|
|
|
|
|
2010-03-05 21:44:18 +00:00
|
|
|
endmenu
|
