summaryrefslogtreecommitdiff
path: root/drivers/xen
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2010-11-08 14:13:35 -0500
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-04-14 11:16:54 -0400
commitc55fa78b13b32d3f19e19cd0c8b9378fdc09e521 (patch)
tree8595a0697b1177763ba42b28908e276a03a8725a /drivers/xen
parenta6360dd37e1a144ed11e6548371bade559a1e4df (diff)
downloadlinux-3.10-c55fa78b13b32d3f19e19cd0c8b9378fdc09e521.tar.gz
linux-3.10-c55fa78b13b32d3f19e19cd0c8b9378fdc09e521.tar.bz2
linux-3.10-c55fa78b13b32d3f19e19cd0c8b9378fdc09e521.zip
xen/pci: Add xen_[find|register|unregister]_device_domain_owner functions.
When the Xen PCI backend is told to enable or disable MSI/MSI-X functions, the initial domain performs these operations. The initial domain needs to know which domain (guest) is going to use the PCI device so when it makes the appropiate hypercall to retrieve the MSI/MSI-X vector it will also assign the PCI device to the appropiate domain (guest). This boils down to us needing a mechanism to find, set and unset the domain id that will be using the device. [v2: EXPORT_SYMBOL -> EXPORT_SYMBOL_GPL.] Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'drivers/xen')
0 files changed, 0 insertions, 0 deletions