qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH V4 0/6] icount: Implement delay algorithm be


From: Sebastian Tanase
Subject: Re: [Qemu-devel] [RFC PATCH V4 0/6] icount: Implement delay algorithm between guest and host clocks
Date: Tue, 22 Jul 2014 17:28:46 +0200 (CEST)


----- Mail original -----
> De: "Paolo Bonzini" <address@hidden>
> À: "Sebastian Tanase" <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden, "peter maydell" 
> <address@hidden>,
> address@hidden, address@hidden, address@hidden, address@hidden, 
> address@hidden,
> address@hidden, address@hidden, address@hidden, address@hidden, 
> address@hidden, "camille begue"
> <address@hidden>, address@hidden
> Envoyé: Mardi 22 Juillet 2014 17:22:18
> Objet: Re: [RFC PATCH V4 0/6] icount: Implement delay algorithm between guest 
> and host clocks
> 
> Il 22/07/2014 17:17, Sebastian Tanase ha scritto:
> >> > That's a bug to fix indeed, then---it should count up from 0
> >> > without
> >> > icount, and icount shouldn't affect this.  Thanks for
> >> > investigating
> >> > it.
> > Just to be sure I don't missunderstand, when you say "without
> > icount"
> > you refer to qemu_icount_bias (aka when the vcpu is inactive),
> > right?
> 
> No, I mean without "-icount", i.e. when QEMU_CLOCK_VIRTUAL is just
> nanoseconds.
> 
> Paolo
> 

When not using "-icount" everything is fine because QEMU_CLOCK_VIRTUAL 
is based on the real clock and the offset; qemu_icount_bias  
doesn't come into play. So the vm_clock_warp_start fix is only for the case 
where we use "-icount".

Sebastian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]