2013-07-23 05:40:58 +08:00
|
|
|
ifeq ($(filter y, $(CONFIG_ARM) $(CONFIG_ARM64)),)
|
2012-09-14 01:28:06 +08:00
|
|
|
obj-$(CONFIG_HOTPLUG_CPU) += cpu_hotplug.o
|
|
|
|
|
endif
|
2012-11-07 04:49:27 +08:00
|
|
|
obj-$(CONFIG_X86) += fallback.o
|
2013-08-07 21:32:12 +08:00
|
|
|
obj-y += grant-table.o features.o balloon.o manage.o
|
|
|
|
|
obj-y += events/
|
2007-07-18 09:37:06 +08:00
|
|
|
obj-y += xenbus/
|
2009-01-08 10:07:11 +08:00
|
|
|
|
2009-08-28 03:46:35 +08:00
|
|
|
nostackp := $(call cc-option, -fno-stack-protector)
|
|
|
|
|
CFLAGS_features.o := $(nostackp)
|
|
|
|
|
|
2014-07-01 01:53:02 +08:00
|
|
|
CFLAGS_efi.o += -fshort-wchar
|
|
|
|
|
|
2012-09-14 01:28:06 +08:00
|
|
|
dom0-$(CONFIG_PCI) += pci.o
|
Features:
* Allow a Linux guest to boot as initial domain and as normal guests
on Xen on ARM (specifically ARMv7 with virtualized extensions).
PV console, block and network frontend/backends are working.
Bug-fixes:
* Fix compile linux-next fallout.
* Fix PVHVM bootup crashing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAABAgAGBQJQbJELAAoJEFjIrFwIi8fJSI4H/32qrQKyF5IIkFKHTN9FYDC1
OxEGc4y47DIQpGUd/PgZ/i6h9Iyhj+I6pb4lCevykwgd0j83noepluZlCIcJnTfL
HVXNiRIQKqFhqKdjTANxVM4APup+7Lqrvqj6OZfUuoxaZ3tSTLhabJ/7UXf2+9xy
g2RfZtbSdQ1sukQ/A2MeGQNT79rh7v7PrYQUYSrqytjSjSLPTqRf75HWQ+eapIAH
X3aVz8Tn6nTixZWvZOK7rAaD4awsFxGP6E46oFekB02f4x9nWHJiCZiXwb35lORb
tz9F9td99f6N4fPJ9LgcYTaCPwzVnceZKqE9hGfip4uT+0WrEqDxq8QmBqI5YtI=
=gxJD
-----END PGP SIGNATURE-----
Merge tag 'stable/for-linus-3.7-arm-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen
Pull ADM Xen support from Konrad Rzeszutek Wilk:
Features:
* Allow a Linux guest to boot as initial domain and as normal guests
on Xen on ARM (specifically ARMv7 with virtualized extensions). PV
console, block and network frontend/backends are working.
Bug-fixes:
* Fix compile linux-next fallout.
* Fix PVHVM bootup crashing.
The Xen-unstable hypervisor (so will be 4.3 in a ~6 months), supports
ARMv7 platforms.
The goal in implementing this architecture is to exploit the hardware
as much as possible. That means use as little as possible of PV
operations (so no PV MMU) - and use existing PV drivers for I/Os
(network, block, console, etc). This is similar to how PVHVM guests
operate in X86 platform nowadays - except that on ARM there is no need
for QEMU. The end result is that we share a lot of the generic Xen
drivers and infrastructure.
Details on how to compile/boot/etc are available at this Wiki:
http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions
and this blog has links to a technical discussion/presentations on the
overall architecture:
http://blog.xen.org/index.php/2012/09/21/xensummit-sessions-new-pvh-virtualisation-mode-for-arm-cortex-a15arm-servers-and-x86/
* tag 'stable/for-linus-3.7-arm-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen: (21 commits)
xen/xen_initial_domain: check that xen_start_info is initialized
xen: mark xen_init_IRQ __init
xen/Makefile: fix dom-y build
arm: introduce a DTS for Xen unprivileged virtual machines
MAINTAINERS: add myself as Xen ARM maintainer
xen/arm: compile netback
xen/arm: compile blkfront and blkback
xen/arm: implement alloc/free_xenballooned_pages with alloc_pages/kfree
xen/arm: receive Xen events on ARM
xen/arm: initialize grant_table on ARM
xen/arm: get privilege status
xen/arm: introduce CONFIG_XEN on ARM
xen: do not compile manage, balloon, pci, acpi, pcpu and cpu_hotplug on ARM
xen/arm: Introduce xen_ulong_t for unsigned long
xen/arm: Xen detection and shared_info page mapping
docs: Xen ARM DT bindings
xen/arm: empty implementation of grant_table arch specific functions
xen/arm: sync_bitops
xen/arm: page.h definitions
xen/arm: hypercalls
...
2012-10-07 06:13:01 +08:00
|
|
|
dom0-$(CONFIG_USB_SUPPORT) += dbgp.o
|
2012-11-08 13:41:13 +08:00
|
|
|
dom0-$(CONFIG_ACPI) += acpi.o $(xen-pad-y)
|
|
|
|
|
xen-pad-$(CONFIG_X86) += xen-acpi-pad.o
|
2012-09-14 01:28:06 +08:00
|
|
|
dom0-$(CONFIG_X86) += pcpu.o
|
2012-10-02 23:00:43 +08:00
|
|
|
obj-$(CONFIG_XEN_DOM0) += $(dom0-y)
|
2011-04-04 20:39:53 +08:00
|
|
|
obj-$(CONFIG_BLOCK) += biomerge.o
|
|
|
|
|
obj-$(CONFIG_XEN_BALLOON) += xen-balloon.o
|
2011-07-09 02:26:21 +08:00
|
|
|
obj-$(CONFIG_XEN_SELFBALLOONING) += xen-selfballoon.o
|
2011-04-04 20:39:53 +08:00
|
|
|
obj-$(CONFIG_XEN_DEV_EVTCHN) += xen-evtchn.o
|
|
|
|
|
obj-$(CONFIG_XEN_GNTDEV) += xen-gntdev.o
|
2011-02-08 06:23:05 +08:00
|
|
|
obj-$(CONFIG_XEN_GRANT_DEV_ALLOC) += xen-gntalloc.o
|
2011-04-04 20:39:53 +08:00
|
|
|
obj-$(CONFIG_XENFS) += xenfs/
|
2010-05-18 00:08:21 +08:00
|
|
|
obj-$(CONFIG_XEN_SYS_HYPERVISOR) += sys-hypervisor.o
|
2011-09-29 19:05:58 +08:00
|
|
|
obj-$(CONFIG_XEN_PVHVM) += platform-pci.o
|
2011-06-18 05:06:20 +08:00
|
|
|
obj-$(CONFIG_XEN_TMEM) += tmem.o
|
2011-04-04 20:39:53 +08:00
|
|
|
obj-$(CONFIG_SWIOTLB_XEN) += swiotlb-xen.o
|
2012-06-07 19:56:51 +08:00
|
|
|
obj-$(CONFIG_XEN_MCE_LOG) += mcelog.o
|
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-14 05:22:20 +08:00
|
|
|
obj-$(CONFIG_XEN_PCIDEV_BACKEND) += xen-pciback/
|
2011-12-17 00:34:33 +08:00
|
|
|
obj-$(CONFIG_XEN_PRIVCMD) += xen-privcmd.o
|
2013-01-24 20:16:59 +08:00
|
|
|
obj-$(CONFIG_XEN_STUB) += xen-stub.o
|
2013-01-24 20:19:47 +08:00
|
|
|
obj-$(CONFIG_XEN_ACPI_HOTPLUG_MEMORY) += xen-acpi-memhotplug.o
|
2013-01-25 15:43:34 +08:00
|
|
|
obj-$(CONFIG_XEN_ACPI_HOTPLUG_CPU) += xen-acpi-cpuhotplug.o
|
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-04 05:03:20 +08:00
|
|
|
obj-$(CONFIG_XEN_ACPI_PROCESSOR) += xen-acpi-processor.o
|
2014-07-01 01:53:02 +08:00
|
|
|
obj-$(CONFIG_XEN_EFI) += efi.o
|
2014-08-28 12:44:12 +08:00
|
|
|
obj-$(CONFIG_XEN_SCSI_BACKEND) += xen-scsiback.o
|
2011-04-04 20:39:53 +08:00
|
|
|
xen-evtchn-y := evtchn.o
|
2010-12-15 02:40:46 +08:00
|
|
|
xen-gntdev-y := gntdev.o
|
2011-02-08 06:23:05 +08:00
|
|
|
xen-gntalloc-y := gntalloc.o
|
2011-12-17 00:34:33 +08:00
|
|
|
xen-privcmd-y := privcmd.o
|
