| commit | c55fa78b13b32d3f19e19cd0c8b9378fdc09e521 | |
| author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Mon, 8 Nov 2010 19:13:35 +0000 (8 14:13 -0500) | ||
| committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Thu, 14 Apr 2011 15:16:54 +0000 (14 11:16 -0400) | ||
| tree | 8595a0697b1177763ba42b28908e276a03a8725a | treesnapshot (tar.gz zip) |
| parent | a6360dd37e1a144ed11e6548371bade559a1e4df | commitdiff |
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>
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>
| arch/x86/include/asm/xen/pci.h | diffblobblamehistory | |
| arch/x86/pci/xen.c | diffblobblamehistory |