search for: drivers_autoprob

On Mon, Aug 21, 2023 at 9:16?AM Shawn.Shao <shawn.shao at jaguarmicro.com> wrote: > > Fix the wrong drivers_autoprobe path name in the document > > Signed-off-by: Shawn.Shao <shawn.shao at jaguarmicro.com> Acked-by: Jason Wang <jasowang at redhat.com> Thanks > --- > Documentation/ABI/testing/sysfs-bus-vdpa | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --...

...> > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci/drivers_autoprobe > > But then we have to worry about races from any devices that might have > been hotplugged in the interim. But, even apart from hot-plugged devices, what about the device we just unbound? There are now 2 host drivers that can handle the device when the autoprobe happens. Is it just...

...> > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci/drivers_autoprobe > > But then we have to worry about races from any devices that might have > been hotplugged in the interim. But, even apart from hot-plugged devices, what about the device we just unbound? There are now 2 host drivers that can handle the device when the autoprobe happens. Is it just...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

...bus/pci/drivers/vfio-pci/remove_id There are actually a number of ways you can do this and the default autoprobe behavior really makes step 3) unnecessary as the driver core will probe any unbound devices as soon as a new_id is added to vfio-pci. That can be changed by: # echo 0 > /sys/bus/pci/drivers_autoprobe But then we have to worry about races from any devices that might have been hotplugged in the interim. To unbind: 1) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/unbind 2) echo ssss:bb:dd.f > /sys/bus/pci/drivers_probe So we don't have to manually remember or hunt down the host...