xen/pciback: xen pci backend driver.
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Tue, 13 Oct 2009 21:22:20 +0000 (17:22 -0400)
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Wed, 20 Jul 2011 00:58:01 +0000 (20:58 -0400)
commit30edc14bf39afde24ef7db2de66c91805db80828
tree1cf5b6f28a3ea4159a09bcef9d11be6d427e3558
parent56299378726d5f2ba8d3c8cbbd13cb280ba45e4f
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>
21 files changed:
drivers/xen/Kconfig
drivers/xen/Makefile
drivers/xen/xen-pciback/Makefile [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space.h [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_capability.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_capability.h [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_capability_msi.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_capability_pm.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_capability_vpd.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_header.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_quirks.c [new file with mode: 0644]
drivers/xen/xen-pciback/conf_space_quirks.h [new file with mode: 0644]
drivers/xen/xen-pciback/controller.c [new file with mode: 0644]
drivers/xen/xen-pciback/passthrough.c [new file with mode: 0644]
drivers/xen/xen-pciback/pci_stub.c [new file with mode: 0644]
drivers/xen/xen-pciback/pciback.h [new file with mode: 0644]
drivers/xen/xen-pciback/pciback_ops.c [new file with mode: 0644]
drivers/xen/xen-pciback/slot.c [new file with mode: 0644]
drivers/xen/xen-pciback/vpci.c [new file with mode: 0644]
drivers/xen/xen-pciback/xenbus.c [new file with mode: 0644]