On Mon, Jun 27, 2016 at 7:19 AM, Paolo Bonzini wrote:
> The new simplified __pvclock_read_cycles does the same computation
> as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info
> pointer) it has to be moved inside the loop. Since the loop is expected
On Mon, Jun 27, 2016 at 7:19 AM, Paolo Bonzini wrote:
> The new simplified __pvclock_read_cycles does the same computation
> as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info
> pointer) it has to be moved inside the loop. Since the loop is expected to
> never roll, this
The new simplified __pvclock_read_cycles does the same computation
as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info
pointer) it has to be moved inside the loop. Since the loop is expected to
never roll, this makes no difference.
Signed-off-by: Paolo Bonzini
The new simplified __pvclock_read_cycles does the same computation
as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info
pointer) it has to be moved inside the loop. Since the loop is expected to
never roll, this makes no difference.
Signed-off-by: Paolo Bonzini
---
4 matches
Mail list logo