From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@qumranet.com>
Subject: Re: [patch 4/4] KVM: allow direct access to PMTimer port
Date: Sun, 25 May 2008 15:31:03 +0300
Message-ID: <48395C07.1050005@qumranet.com>
References: <20080524234342.983197667@localhost.localdomain> <20080525000036.710955693@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194]:59983
	"EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756412AbYEYMbF (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 25 May 2008 08:31:05 -0400
In-Reply-To: <20080525000036.710955693@localhost.localdomain>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Marcelo Tosatti wrote:
> There's not much point in exiting for pmtimer reads, since it runs at a
> fixed clock rate and its start value is undefined.
>   

On a migration farm with lots of different hardware, eventually all 
guests will have migrated and none of them will be able to use the 
passthrough port.

What about emulating pmtimer in the host kernel instead of userspace?  
It increases the hit from 1 exit to 3 exits, but they're much faster exits.

-- 
error compiling committee.c: too many arguments to function