Hello, On Sat, Oct 24, 2026 at 06:56:34AM +0200, Greg Kroah-Hartman wrote: > So what is the real use case here, taking any type of any device and > thinking you can bind a random kernel driver to it and it will work ok? > You all have specific platform and pci vfio drivers, why not use the > proper device ids there instead, or better yet, bake-in this type of > functionality into the bus-specific logic so that you can have generic > userspace control of a device (like usbfs and uio does today)?
Also note that even if the platform and pci busses implement bus-specific code to pass a given device to userspace and/or a VM, you need proper unbind support in the driver currently managing the device (or cripple the mechanism to only work for devices that were not bound to a host driver before). The more I think about this taint, the more I believe the commit should be reverted and replaced by a some stop gaps for driver_override. (Be it a taint or better yet https://lore.kernel.org/all/0f7446324f6a0c8f0153d6532d92a6eeecd6a308.1790612298.git.u.kleine-koe...@baylibre.com/ .) Best regards Uwe
signature.asc
Description: PGP signature
