From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [patch 00/15] pvclock vsyscall support + KVM hypervisor support
Date: Tue, 16 Oct 2012 14:56:19 -0300
Message-ID: <20121016175619.194848607@redhat.com>
Cc: johnstul@us.ibm.com, jeremy@goop.org
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:30724 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754953Ab2JPSWY (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 16 Oct 2012 14:22:24 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This patchset, based on earlier work by Jeremy Fitzhardinge, implements
paravirtual clock vsyscall support.

It should be possible to implement Xen support relatively easily.

It reduces clock_gettime from 500 cycles to 200 cycles 
on my testbox (including an mfence, that measurement).

NOTE: exporting pvclock tsc stable bit if the guest TSCs are
not synchronized is incorrect, next version will have that fixed.

Please review.