diff options
| author | Jan Beulich <jbeulich@suse.com> | 2011-09-18 00:12:19 +0100 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2011-09-18 00:12:19 +0100 |
| commit | 7620c0cf9a4df9cff19be020bf84f8a71cc31d8d (patch) | |
| tree | 4e0695f43d0d1ad85c0fcaf1a4d59fb5b7859740 /xen/include/xlat.lst | |
| parent | 21844b0e32e77c9e1a600b9279a859a7ffe01844 (diff) | |
| download | xen-7620c0cf9a4df9cff19be020bf84f8a71cc31d8d.tar.gz xen-7620c0cf9a4df9cff19be020bf84f8a71cc31d8d.tar.bz2 xen-7620c0cf9a4df9cff19be020bf84f8a71cc31d8d.zip | |
PCI multi-seg: add new physdevop-s
The new PHYSDEVOP_pci_device_add is intended to be extensible, with a
first extension (to pass the proximity domain of a device) added right
away.
A couple of directly related functions at once get adjusted to account
for the segment number.
Should we deprecate the PHYSDEVOP_manage_pci_* sub-hypercalls?
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Diffstat (limited to 'xen/include/xlat.lst')
| -rw-r--r-- | xen/include/xlat.lst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/xen/include/xlat.lst b/xen/include/xlat.lst index d31ed838d2..fcf692255b 100644 --- a/xen/include/xlat.lst +++ b/xen/include/xlat.lst @@ -65,6 +65,8 @@ ? physdev_irq_status_query physdev.h ? physdev_manage_pci physdev.h ? physdev_manage_pci_ext physdev.h +? physdev_pci_device physdev.h +? physdev_pci_device_add physdev.h ? physdev_pci_mmcfg_reserved physdev.h ? physdev_unmap_pirq physdev.h ? physdev_restore_msi physdev.h |