Aw: [PATCH v3 0/7] USB hostdev: allow addressing by port

2025-09-04 Thread Maximilian Martin via Devel
PingAm 18.08.25, 16:40 schrieb Maximilian Martin via Devel lists.libvirt.org>: Currently, only vendor/product and bus/device matching are supported for USB host devices. Neither of these provide a stable and persistent way of assigning a guest a specific host device. Vendor/product can

[PATCH v3 7/7] docs: add description for USB port matching

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin Adds documentation for the new USB bus/port addressing. The new "port" attribute is explained. Resolves: https://gitlab.com/libvirt/libvirt/-/issues/513 Signed-off-by: Maximilian Martin --- docs/formatdomain.rst | 29 - 1 file changed, 16 ins

[PATCH v3 4/7] schema: add USB port attribute

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin Adds USB bus/port addressing the domain XML file schema. Optionally, the physical USB port can be declared instead of the USB device address. Signed-off-by: Maximilian Martin --- src/conf/schemas/domaincommon.rng | 11 --- 1 file changed, 8 insertions(+), 3 dele

[PATCH v3 1/7] tests: validate an XML config with USB vendor/product set

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin The USB vendor/product is usually translated into a device/bus at startup using the hostdev logic. We don't run the latter in the unit test suite, but we can fake it by hardcoding a translation. This demonstrates that we format the command line with the normal device/bus p

[PATCH v3 6/7] nodedev: add USB port to nodedev XML

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin This adds the physical USB port to the capabilities of a USB device in nodedev XML. example: 1.4 Signed-off-by: Maximilian Martin --- src/conf/node_device_conf.c | 5 +++ src/conf/node_device_conf.h | 1 + src/conf/schemas/basictype

[PATCH v3 5/7] tests: validate an XML config with USB bus/port set

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin USB bus/port addressing is translated into a bus/device addressing at startup using the hostdev logic. This test covers XML parsing and CLI formatting for bus/port addressing. Signed-off-by: Maximilian Martin --- ...ostdev-usb-address-port.x86_64-latest.args | 36 ++

[PATCH v3 3/7] domain_conf, virhostdev, virusb, virusb test: add bus/port matching

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin This patch implements USB bus/port matching. In addition to vendor/product and bus/device matching, bus/port matching is implemented. This involves additions and refactorings in the domain configuration, host device handling, and USB helpers. Also, test methods are refacto

[PATCH v3 2/7] virusb test data: add devpath files for port addressing

2025-08-18 Thread Maximilian Martin via Devel
From: Maximilian Martin This patch adds devpath files to the virusb test data. These files are mockups for the USB sysfs files that contain the port of a USB device in dotted notation. They are used for testing of USB bus/port matching. Signed-off-by: Maximilian Martin --- tests/virusbtestdata

[PATCH v3 0/7] USB hostdev: allow addressing by port

2025-08-18 Thread Maximilian Martin via Devel
Currently, only vendor/product and bus/device matching are supported for USB host devices. Neither of these provide a stable and persistent way of assigning a guest a specific host device. Vendor/product can be ambiguous. Device numbers change on every enumeration. This patch adds a bus/port ma

Re: [PATCH 0/4] USB hostdev: allow addressing by port

2025-06-27 Thread Maximilian Martin via Devel
u, Jun 26, 2025 at 06:01:30PM +0200, Maximilian Martin wrote: Am 23.06.2025 um 16:50 schrieb Daniel P. Berrangé: On Mon, Apr 21, 2025 at 09:38:34PM +0200, Maximilian Martin via Devel wrote: This resubmission splits up the previous patch into multiple patches and incorporates review comme

Re: [PATCH 0/4] USB hostdev: allow addressing by port

2025-06-26 Thread Maximilian Martin via Devel
Am 23.06.2025 um 16:50 schrieb Daniel P. Berrangé: On Mon, Apr 21, 2025 at 09:38:34PM +0200, Maximilian Martin via Devel wrote: This resubmission splits up the previous patch into multiple patches and incorporates review comments from Michal Prívozník. Currently, only vendor/product and bus

Re: [PATCH 0/4] USB hostdev: allow addressing by port

2025-06-26 Thread Maximilian Martin via Devel
Am 23.06.2025 um 16:32 schrieb Daniel P. Berrangé via Devel: On Mon, Jun 23, 2025 at 04:11:25PM +0200, Michal Prívozník via Devel wrote: On 4/21/25 21:38, Maximilian Martin via Devel wrote: This resubmission splits up the previous patch into multiple patches and incorporates review comments

Re: [PATCH 0/4] USB hostdev: allow addressing by port

2025-06-22 Thread Maximilian Martin via Devel
Bump :) Am 20.05.2025 um 20:49 schrieb Maximilian Martin: Friendly ping :) Am 21.04.2025 um 21:38 schrieb Maximilian Martin via Devel: This resubmission splits up the previous patch into multiple patches and incorporates review comments from Michal Prívozník. Currently, only vendor/product

Re: [PATCH 0/4] USB hostdev: allow addressing by port

2025-05-20 Thread Maximilian Martin via Devel
Friendly ping :) Am 21.04.2025 um 21:38 schrieb Maximilian Martin via Devel: This resubmission splits up the previous patch into multiple patches and incorporates review comments from Michal Prívozník. Currently, only vendor/product and bus/device matching are supported for USB host devices

[PATCH 4/4] docs: add description for USB port matching

2025-04-21 Thread Maximilian Martin via Devel
From: Maximilian Martin Adds documentation for the new USB bus/port addressing. The new "port" attribute is explained. Signed-off-by: Maximilian Martin --- docs/formatdomain.rst | 29 - 1 file changed, 16 insertions(+), 13 deletions(-) diff --git a/docs/formatdomai

[PATCH 2/4] domain_conf, virhostdev, virusb, virusb test: add bus/port matching

2025-04-21 Thread Maximilian Martin via Devel
From: Maximilian Martin This patch implements USB bus/port matching. In addition to vendor/product and bus/device matching, bus/port matching is implemented. This involves additions and refactorings in the domain configuration, host device handling, and USB helpers. Also, test methods are refacto

[PATCH 0/4] USB hostdev: allow addressing by port

2025-04-21 Thread Maximilian Martin via Devel
This resubmission splits up the previous patch into multiple patches and incorporates review comments from Michal Prívozník. Currently, only vendor/product and bus/device matching are supported for USB host devices. Neither of these provide a stable and persistent way of assigning a guest a spec

[PATCH 1/4] virusb test data: add devpath files for port addressing

2025-04-21 Thread Maximilian Martin via Devel
From: Maximilian Martin This patch adds devpath files to the virusb test data. These files are mockups for the USB sysfs files that contain the port of a USB device in dotted notation. They are used for testing of USB bus/port matching. Signed-off-by: Maximilian Martin --- tests/virusbtestdata

[PATCH 3/4] schema: add USB port attribute

2025-04-21 Thread Maximilian Martin via Devel
From: Maximilian Martin Adds USB bus/port addressing the domain XML file schema. Optionally, the physical USB port can be declared instead of the USB device address. Signed-off-by: Maximilian Martin --- src/conf/schemas/domaincommon.rng | 11 --- 1 file changed, 8 insertions(+), 3 dele

Re: [PATCH] USB hostdev: allow addressing by port

2025-03-25 Thread Maximilian Martin via Devel
Ping :) It's a much requested feature and certainly a low-hanging fruit. I'm happy to integrate feedback! Am 17.03.2025 um 21:59 schrieb Maximilian Martin via Devel: From: Maximilian Martin Currently, only vendor/product and bus/device matching are supported for USB host device

[PATCH] USB hostdev: allow addressing by port

2025-03-18 Thread Maximilian Martin via Devel
From: Maximilian Martin Currently, only vendor/product and bus/device matching are supported for USB host devices. Neither of these provide a stable and persistent way of assigning a guest a specific host device. Vendor/product can be ambiguous. Device numbers change on every enumeration. Thi