BALATON Zoltan <bala...@eik.bme.hu> writes: > On Thu, 29 Feb 2024, Sven Schnelle wrote: >> BALATON Zoltan <bala...@eik.bme.hu> writes: >> Yes, i changed it to describe the new method: >> >> /* >> * Some windows drivers make the device spin waiting for a memory location >> * to change. If we have executed more than LSI_MAX_INSN instructions then >> * assume this is the case and start a timer. Until the timer fires, the >> * host CPU has a chance to run and change the memory location. > > Is that the host or guest CPU? I thought the guest vcpu needs to get a > chance to do something about this but maybe I did not get the problem > at all.
Of course it's the guest CPU. I'll wait for other review comments and fix it in the next version. Thanks! Sven
