On 04/12/2011 11:50 PM, Edgar E. Iglesias wrote:
I also tested the code and it works beautifully for my testcases!
iothread & icount ran faster than icount without iothread.
That's very good news, thanks!
Paolo
On Tue, Apr 12, 2011 at 03:26:39PM +0200, Paolo Bonzini wrote:
> On 04/12/2011 11:26 AM, Jan Kiszka wrote:
> > On 2011-04-12 10:44, Paolo Bonzini wrote:
> >> This series finally fixes -icount with iothread and avoids deadlocks
> >> due to the vm_clock not making progress when the VM is stopped.
> >
On 04/12/2011 11:26 AM, Jan Kiszka wrote:
On 2011-04-12 10:44, Paolo Bonzini wrote:
This series finally fixes -icount with iothread and avoids deadlocks
due to the vm_clock not making progress when the VM is stopped.
The crux of the fix is in patch 1, while patch 2 implements the
"clock warping"
On 2011-04-12 10:44, Paolo Bonzini wrote:
> This series finally fixes -icount with iothread and avoids deadlocks
> due to the vm_clock not making progress when the VM is stopped.
> The crux of the fix is in patch 1, while patch 2 implements the
> "clock warping" that fixes deadlocks in v2. Clock w
This series finally fixes -icount with iothread and avoids deadlocks
due to the vm_clock not making progress when the VM is stopped.
The crux of the fix is in patch 1, while patch 2 implements the
"clock warping" that fixes deadlocks in v2. Clock warping uses
the nanosecond resolution rt_clock tim
