On Fri, Aug 30, 2024 at 10:34:42AM +0800, Cheng Xu wrote: > > > On 8/29/24 6:09 PM, Leon Romanovsky wrote: > > On Wed, Aug 28, 2024 at 02:09:41PM +0800, Cheng Xu wrote: > >> Driver may probe again while hardware is destroying the internal > >> resources allocated for previous probing > > > > How is it possible? > > > > The resources I mentioned is totally unseen to driver, it's something related > to our device management part in hypervisor, so it won't cause host resources > leak, and the cleanup/reset process may take a long time. For these reason, > we don't wait the completion of the cleanup/reset in the remove routing. > Instead, the driver will wait the device status become ready in probe routing > (In most cases, the hardware will have enough time to finish the cleanup/reset > before the second probe), so that we can boost the remove process. And why don't hypervisor wait for the device to be ready before giving it to VM? Why do you need to complicate the probe routine to overcome the hypervisor behavior? Thanks > > Thanks, > Cheng Xu >
