diff options
author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2009-10-13 17:22:20 -0400 |
---|---|---|
committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2011-07-19 20:58:01 -0400 |
commit | 30edc14bf39afde24ef7db2de66c91805db80828 (patch) | |
tree | 1cf5b6f28a3ea4159a09bcef9d11be6d427e3558 /drivers/xen/xen-pciback/pciback_ops.c | |
parent | 56299378726d5f2ba8d3c8cbbd13cb280ba45e4f (diff) |
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>
Diffstat (limited to 'drivers/xen/xen-pciback/pciback_ops.c')
-rw-r--r-- | drivers/xen/xen-pciback/pciback_ops.c | 131 |
1 files changed, 131 insertions, 0 deletions
diff --git a/drivers/xen/xen-pciback/pciback_ops.c b/drivers/xen/xen-pciback/pciback_ops.c new file mode 100644 index 000000000000..2b9a93e1fdee --- /dev/null +++ b/drivers/xen/xen-pciback/pciback_ops.c | |||
@@ -0,0 +1,131 @@ | |||
1 | /* | ||
2 | * PCI Backend Operations - respond to PCI requests from Frontend | ||
3 | * | ||
4 | * Author: Ryan Wilson <hap9@epoch.ncsc.mil> | ||
5 | */ | ||
6 | #include <linux/module.h> | ||
7 | #include <linux/wait.h> | ||
8 | #include <linux/bitops.h> | ||
9 | #include <xen/events.h> | ||
10 | #include <linux/sched.h> | ||
11 | #include "pciback.h" | ||
12 | |||
13 | int verbose_request; | ||
14 | module_param(verbose_request, int, 0644); | ||
15 | |||
16 | /* Ensure a device is "turned off" and ready to be exported. | ||
17 | * (Also see pciback_config_reset to ensure virtual configuration space is | ||
18 | * ready to be re-exported) | ||
19 | */ | ||
20 | void pciback_reset_device(struct pci_dev *dev) | ||
21 | { | ||
22 | u16 cmd; | ||
23 | |||
24 | /* Disable devices (but not bridges) */ | ||
25 | if (dev->hdr_type == PCI_HEADER_TYPE_NORMAL) { | ||
26 | pci_disable_device(dev); | ||
27 | |||
28 | pci_write_config_word(dev, PCI_COMMAND, 0); | ||
29 | |||
30 | dev->is_busmaster = 0; | ||
31 | } else { | ||
32 | pci_read_config_word(dev, PCI_COMMAND, &cmd); | ||
33 | if (cmd & (PCI_COMMAND_INVALIDATE)) { | ||
34 | cmd &= ~(PCI_COMMAND_INVALIDATE); | ||
35 | pci_write_config_word(dev, PCI_COMMAND, cmd); | ||
36 | |||
37 | dev->is_busmaster = 0; | ||
38 | } | ||
39 | } | ||
40 | } | ||
41 | /* | ||
42 | * Now the same evtchn is used for both pcifront conf_read_write request | ||
43 | * as well as pcie aer front end ack. We use a new work_queue to schedule | ||
44 | * pciback conf_read_write service for avoiding confict with aer_core | ||
45 | * do_recovery job which also use the system default work_queue | ||
46 | */ | ||
47 | void test_and_schedule_op(struct pciback_device *pdev) | ||
48 | { | ||
49 | /* Check that frontend is requesting an operation and that we are not | ||
50 | * already processing a request */ | ||
51 | if (test_bit(_XEN_PCIF_active, (unsigned long *)&pdev->sh_info->flags) | ||
52 | && !test_and_set_bit(_PDEVF_op_active, &pdev->flags)) { | ||
53 | queue_work(pciback_wq, &pdev->op_work); | ||
54 | } | ||
55 | /*_XEN_PCIB_active should have been cleared by pcifront. And also make | ||
56 | sure pciback is waiting for ack by checking _PCIB_op_pending*/ | ||
57 | if (!test_bit(_XEN_PCIB_active, (unsigned long *)&pdev->sh_info->flags) | ||
58 | && test_bit(_PCIB_op_pending, &pdev->flags)) { | ||
59 | wake_up(&aer_wait_queue); | ||
60 | } | ||
61 | } | ||
62 | |||
63 | /* Performing the configuration space reads/writes must not be done in atomic | ||
64 | * context because some of the pci_* functions can sleep (mostly due to ACPI | ||
65 | * use of semaphores). This function is intended to be called from a work | ||
66 | * queue in process context taking a struct pciback_device as a parameter */ | ||
67 | |||
68 | void pciback_do_op(struct work_struct *data) | ||
69 | { | ||
70 | struct pciback_device *pdev = | ||
71 | container_of(data, struct pciback_device, op_work); | ||
72 | struct pci_dev *dev; | ||
73 | struct xen_pci_op *op = &pdev->sh_info->op; | ||
74 | |||
75 | dev = pciback_get_pci_dev(pdev, op->domain, op->bus, op->devfn); | ||
76 | |||
77 | if (dev == NULL) | ||
78 | op->err = XEN_PCI_ERR_dev_not_found; | ||
79 | else { | ||
80 | switch (op->cmd) { | ||
81 | case XEN_PCI_OP_conf_read: | ||
82 | op->err = pciback_config_read(dev, | ||
83 | op->offset, op->size, &op->value); | ||
84 | break; | ||
85 | case XEN_PCI_OP_conf_write: | ||
86 | op->err = pciback_config_write(dev, | ||
87 | op->offset, op->size, op->value); | ||
88 | break; | ||
89 | #ifdef CONFIG_PCI_MSI | ||
90 | case XEN_PCI_OP_enable_msi: | ||
91 | op->err = pciback_enable_msi(pdev, dev, op); | ||
92 | break; | ||
93 | case XEN_PCI_OP_disable_msi: | ||
94 | op->err = pciback_disable_msi(pdev, dev, op); | ||
95 | break; | ||
96 | case XEN_PCI_OP_enable_msix: | ||
97 | op->err = pciback_enable_msix(pdev, dev, op); | ||
98 | break; | ||
99 | case XEN_PCI_OP_disable_msix: | ||
100 | op->err = pciback_disable_msix(pdev, dev, op); | ||
101 | break; | ||
102 | #endif | ||
103 | default: | ||
104 | op->err = XEN_PCI_ERR_not_implemented; | ||
105 | break; | ||
106 | } | ||
107 | } | ||
108 | /* Tell the driver domain that we're done. */ | ||
109 | wmb(); | ||
110 | clear_bit(_XEN_PCIF_active, (unsigned long *)&pdev->sh_info->flags); | ||
111 | notify_remote_via_irq(pdev->evtchn_irq); | ||
112 | |||
113 | /* Mark that we're done. */ | ||
114 | smp_mb__before_clear_bit(); /* /after/ clearing PCIF_active */ | ||
115 | clear_bit(_PDEVF_op_active, &pdev->flags); | ||
116 | smp_mb__after_clear_bit(); /* /before/ final check for work */ | ||
117 | |||
118 | /* Check to see if the driver domain tried to start another request in | ||
119 | * between clearing _XEN_PCIF_active and clearing _PDEVF_op_active. | ||
120 | */ | ||
121 | test_and_schedule_op(pdev); | ||
122 | } | ||
123 | |||
124 | irqreturn_t pciback_handle_event(int irq, void *dev_id) | ||
125 | { | ||
126 | struct pciback_device *pdev = dev_id; | ||
127 | |||
128 | test_and_schedule_op(pdev); | ||
129 | |||
130 | return IRQ_HANDLED; | ||
131 | } | ||