diff options
author | Roger Pau Monne <roger.pau@citrix.com> | 2025-02-19 12:20:55 +0300 |
---|---|---|
committer | Juergen Gross <jgross@suse.com> | 2025-03-21 10:15:26 +0300 |
commit | 5ccf1b8ae76ddf348e02a0d1564ff9baf8b6c415 (patch) | |
tree | 6f371a87d60f987f3873b62c6ed4bd8ba5b57e40 /tools/perf/scripts/python/libxed.py | |
parent | 421d62f47b7a61794f04ddd9ec2e4fa2e209da90 (diff) | |
download | linux-5ccf1b8ae76ddf348e02a0d1564ff9baf8b6c415.tar.xz |
xen/pci: Do not register devices with segments >= 0x10000
The current hypercall interface for doing PCI device operations always uses
a segment field that has a 16 bit width. However on Linux there are buses
like VMD that hook up devices into the PCI hierarchy at segment >= 0x10000,
after the maximum possible segment enumerated in ACPI.
Attempting to register or manage those devices with Xen would result in
errors at best, or overlaps with existing devices living on the truncated
equivalent segment values. Note also that the VMD segment numbers are
arbitrarily assigned by the OS, and hence there would need to be some
negotiation between Xen and the OS to agree on how to enumerate VMD
segments and devices behind them.
Skip notifying Xen about those devices. Given how VMD bridges can
multiplex interrupts on behalf of devices behind them there's no need for
Xen to be aware of such devices for them to be usable by Linux.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Juergen Gross <jgross@suse.com>
Message-ID: <20250219092059.90850-2-roger.pau@citrix.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions