[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH, RFC 0/7] PCI multi-segment support

In order for Xen to be able to boot on systems with multiple PCI segments
(also called domains), a number of changes are necessary to the
hypervisor, the hypercall interface, the tools, and the Dom0 kernel, as
in most code paths and definitions there were not even provisions for
passing a segment number.

The hypercall interface changes may need some discussion before
applying the patches, in particular

- whether the way PHYSDEVOP_map_pirq gets re-used is acceptable,
  or whether alternatively we should define a replacement one sub-
- whether PHYSDEVOP_manage_pci_* should be deprecated
- whether the bit assignments for the four uses of machine_bdf in
  the domctl interface can be re-defined

Additionally, in the AMD IOMMU code there are two places where I
was unable to identify how the segment value ought to be retrieved.
Since I'm unaware of multi-segment AMD-based systems, imo this
should not be a reason to not commit the changes proposed.

1: introduce notion of PCI segments
2: add new physdevop-s
3: adjust domctl interface
4: VT-d specific adjustments
5: AMD-IOMMU specific adjustments
6: Pass-through adjustments
7: config space accessor adjustments

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.