From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Desfossez <ju@klipix.org>
Subject: vread in kvm_clock
Date: Wed, 15 Dec 2010 15:16:37 -0500
Message-ID: <4D092225.3000300@klipix.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from debowa.klipix.org ([88.191.83.101]:56820 "EHLO
	debowa.klipix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754249Ab0LOUjn (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 15 Dec 2010 15:39:43 -0500
Received: from localhost.localdomain (dsl-69-171-152-153.acanac.net [69.171.152.153])
	by debowa.klipix.org (Postfix) with ESMTP id 4508E1E251A
	for <kvm@vger.kernel.org>; Wed, 15 Dec 2010 21:16:39 +0100 (CET)
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi,

I'm currently working with the kvm clocksource and I'm wondering if we 
could implement the vread function for this clock source when we are 
running on a host with constant_tsc.
If I understand correctly the hv_clock structure is per_cpu because of 
the eventual frequency changes, but in the case of constant_tsc (and 
after validation that the TSC is synchronized across all the cores) I 
think we could have a working vread function.

In case of migration, could we have a fallback in case we detect we end 
up on a CPU without constant_tsc ?

Any advice/explanation would be greatly appreciated !

Thanks,

Julien