Re: [PATCH] kvm: x86: add trace event for pvclock updates
From: Marcelo Tosatti
Date: Mon Nov 10 2014 - 20:19:26 EST
On Wed, Nov 05, 2014 at 11:46:42AM -0800, David Matlack wrote:
> The new trace event records:
> * the id of vcpu being updated
> * the pvclock_vcpu_time_info struct being written to guest memory
>
> This is useful for debugging pvclock bugs, such as the bug fixed by
> "[PATCH] kvm: x86: Fix kvm clock versioning.".
>
> Signed-off-by: David Matlack <dmatlack@xxxxxxxxxx>
So you actually hit that bug in practice? Can you describe the
scenario?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/