BTW I have a series here that fixes up some of the QOM issues with vfio, but
I'm guessing it's a little too close to freeze for this?
Please send and we'll see.
Thanks,
C.
On 15/07/2025 06:49, Cédric Le Goater wrote:
On 7/11/25 13:38, Mark Cave-Ayland wrote:
On 10/07/2025 16:47, John Levon wrote:
(added Cedric)
ah. Thanks Mark.
This reminds me that we should have maintainers/reviewers
that can send PRs for the vfio-user component.
John,
Could you please sen
On 7/11/25 13:38, Mark Cave-Ayland wrote:
On 10/07/2025 16:47, John Levon wrote:
(added Cedric)
ah. Thanks Mark.
This reminds me that we should have maintainers/reviewers
that can send PRs for the vfio-user component.
John,
Could you please send a patch adding me and Mark may be ?
Cover
On 10/07/2025 16:47, John Levon wrote:
(added Cedric)
Coverity reported:
CID 1611806: Concurrent data access violations (BAD_CHECK_OF_WAIT_COND)
A wait is performed without a loop. If there is a spurious wakeup, the
condition may not be satisfied.
Fix this by checking ->state for VFIO_PROXY_
Coverity reported:
CID 1611806: Concurrent data access violations (BAD_CHECK_OF_WAIT_COND)
A wait is performed without a loop. If there is a spurious wakeup, the
condition may not be satisfied.
Fix this by checking ->state for VFIO_PROXY_CLOSED in a loop.
Signed-off-by: John Levon
---
hw/vfio
