public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: Pass through the host kernel's IO delay port
Date: Mon, 22 Jun 2009 12:31:27 +0300	[thread overview]
Message-ID: <4A3F4F6F.6090209@redhat.com> (raw)
In-Reply-To: <1245406553-22013-1-git-send-email-pbonzini@redhat.com>

On 06/19/2009 01:15 PM, Paolo Bonzini wrote:
> From: Paolo Bonzini<pbonzini@redhat.com>
>
> 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


  reply	other threads:[~2009-06-22  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 10:15 [PATCH] KVM: SVM: Pass through the host kernel's IO delay port Paolo Bonzini
2009-06-22  9:31 ` Avi Kivity [this message]
2009-06-22 10:11   ` Paolo Bonzini
2009-06-22 10:24     ` Gleb Natapov
2009-06-22 11:11     ` Avi Kivity
2009-06-22 17:35 ` Marcelo Tosatti
2009-06-22 17:57   ` Paolo Bonzini
2009-06-22 18:30     ` Marcelo Tosatti
2009-06-23  6:59       ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A3F4F6F.6090209@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox