On 17.10.2025 16:14, Roger Pau Monne wrote:
> Otherwise it's not possible for device models to map IRQs of devices on
> segments different than 0. Keep the same function prototype and pass the
> segment in the high 16bits of the bus parameter, like it's done for the
> hypercall itself.
While easiest, that's an odd interface, though. Should, at the very least the
function parameter then be named e.g. "segbus", along the lines of "devfn"?
> Fixes: 7620c0cf9a4d ("PCI multi-seg: add new physdevop-s")
This commit wasn't about tool stack uses of the interfaces at all.
Jan
