From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [patch 00/18] pvclock vsyscall support + KVM hypervisor support (v2)
Date: Wed, 24 Oct 2012 11:13:40 -0200
Message-ID: <20121024131340.742340256@redhat.com>
Cc: johnstul@us.ibm.com, jeremy@goop.org, glommer@parallels.com,
	zamsden@gmail.com, gleb@redhat.com, avi@redhat.com,
	pbonzini@redhat.com
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:49223 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S934137Ab2JXNRb (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 24 Oct 2012 09:17:31 -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.

Please review.

>>From my POV, this is ready to merge.

v2: 
- Do not allow visibility of different <system_timestamp, tsc_timestamp> 
tuples.
- Add option to disable vsyscall.