From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: SVM: Pass through the host kernel's IO delay port Date: Mon, 22 Jun 2009 12:31:27 +0300 Message-ID: <4A3F4F6F.6090209@redhat.com> References: <1245406553-22013-1-git-send-email-pbonzini@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx2.redhat.com ([66.187.237.31]:40222 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750765AbZFVJah (ORCPT ); Mon, 22 Jun 2009 05:30:37 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n5M9UeG3026638 for ; Mon, 22 Jun 2009 05:30:40 -0400 In-Reply-To: <1245406553-22013-1-git-send-email-pbonzini@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/19/2009 01:15 PM, Paolo Bonzini wrote: > From: Paolo Bonzini > > KVM's optimization of guest port 80 accesses was removed last May 11 > in commit 99f85a. However, this probably has speed penalties. I don't > have a machine to test but the equivalent VMX patch (fdef3ad) reported > a speedup of 3-5%, and on the Xen mailing list it was mentioned that on > Xen passing port 80 through had positive effects on startup speed. > > We can enable passthrough to the same port the host kernel uses instead. > Since we don't tell the guest to use 0xed, this won't help. If we can tell the guest, we can just tell it not to use any port at all, since this is a virtualized environment and there's no buggy hardware to please. We could speed it up by trapping and emulating the port write in the kernel instead of letting userspace handle it (should be faster than passthrough on newer hosts). I'd like to make is configurable from userspace though, the kernel has no business trapping random ports. -- error compiling committee.c: too many arguments to function