Re: Remove condition variables from injection wait logic.

> On 21 Aug 2025, at 04:02, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> I would not object to that if that's the actual consensus as we don't
> have a strong requirement for condition variables when it comes to
> testing. That's just a more efficient implementation, and it makes
> the tests faster. If we do that, I'd suggest to choose a cap and a
> variable wait time, that increases across iterations to still make the
> wait more responsive on faster machines.

I want to do a test for suspected VM corruption (1).
I need a way to do injection point that can be kill-9-ed without corruption.
So I can just use Kirill's patch to develop my test, thanks! I do not need it committed until the work is over.

So far there are no tests in the tree that need this functionality in injection points.
And even when we will have such a test that needs this kind of sleep, it is only required if injection point is in critical section. Not for every injection point wait.

Also, CondVar might be fixed and allowed to be used in critical section (2). AIO needs it anyway.

Let's wait for (1) or (2), then decide if we need to do something with injection point waiting.

Thanks you both for working on these tools!

Best regards, Andrey Borodin.