From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [RFC] Moving the kvm ioapic, pic, and pit back to userspace
Date: Thu, 10 Jun 2010 05:59:03 +0300
Message-ID: <4C1054F7.4030904@redhat.com>
References: <4C0D0FB7.80709@redhat.com> <1A42CE6F5F474C41B63392A5F80372B21F26E155@shsmsx501.ccr.corp.intel.com> <4C0FBBD8.6080708@redhat.com> <1A42CE6F5F474C41B63392A5F80372B21F26E3A1@shsmsx501.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: KVM list <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
To: "Dong, Eddie" <eddie.dong@intel.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:45570 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752708Ab0FJC7L (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 9 Jun 2010 22:59:11 -0400
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B21F26E3A1@shsmsx501.ccr.corp.intel.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 06/10/2010 05:37 AM, Dong, Eddie wrote:
> Avi Kivity wrote:
>    
>> On 06/09/2010 06:59 PM, Dong, Eddie wrote:
>>      
>>> Besides VF IO interrupt and timer interrupt introduced performance
>>> overhead risk,
>>>        
>> VF usually uses MSI
>>      
> Typo, I mean PV IO.
>    

That also uses MSI these days.

> A VF interrupt usually happens in 4-8KHZ. How about the virtio?
> I assume virtio will be widely used together w/ leagcy guest with INTx mode.
>    

True, but in time it will be replaced by MSI.

Note without vhost virtio is also in userspace, so there are lots of 
exits anyway for the status register.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.