On Thu, Jun 22, 2023 at 12:32:33PM +0000, Parav Pandit wrote:
> Provisioning driver usually do not attach to the member device directly.
> This requires device reset, followed by reaching _DRIVER stage, querying
> features etc and config area.
> And unbinding it and second reset by member driver. Ugh.
> Provisioning driver also needs to get the state or capabilities even when
> member driver is already attached.
> So config space is not much a gain either.
Actually it's RO so you *can* read it without any issues:
- block guest access to status
- check DRIVER.
If set:
- read features, config
If not set:
- read features, config
- reset
I am not saying it is elegant but then all of vdpa pile of
hacks is not elegant.
And I am all for building something better but we didn't
build it yet.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
