Replace bus/slot/function with full PCI paths

[DemiMarie]

How to file a helpful issue

The problem you're addressing (if any)

PCI devices are currently assigned via bus/slot/function, which is not a stable identifier.

The solution you'd like

Use PCI paths instead, which are much more likely to be stable.

The value to a user, and who that user might be

Users will be less likely to have problems with PCI device renumbering.

[jamke]

We had several discussions on this topic:

#7792
#7883

[marmarek]

Use PCI paths instead, which are much more likely to be stable.

Please be more specific what exactly you mean. sysfs path of the device? Can you give a specific example (that can be used as a device identifier, so meets qrexec service argument allowed character set)?

[DemiMarie]

Use PCI paths instead, which are much more likely to be stable.

Please be more specific what exactly you mean. sysfs path of the device?

Physical path to the device, as defined by the sequence of PCI switches that must be traversed. I think this corresponds to sysfs path.

Can you give a specific example (that can be used as a device identifier, so meets qrexec service argument allowed character set)?

One can turn the sysfs path into an identifier by escaping.