From: Paolo Bonzini <pbonzini@redhat.com>
To: Avi Kivity <avi@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:11:59 +0200 [thread overview]
Message-ID: <4A3F58EF.8010206@redhat.com> (raw)
In-Reply-To: <4A3F4F6F.6090209@redhat.com>
Avi Kivity wrote:
> 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.
Won't the guest do that automatically through DMI?
I think we have four cases:
1) non-buggy chipset, host uses 0x80 and guest cannot crash the machine;
this is okay.
2) buggy chipset, both host and guest use 0xed thanks to DMI detection;
and (since 0x80 is not passthrough) the guest cannot crash the machine,
so this is okay.
3) host is given explicit io_delay=0xed, but the guest isn't. However,
0x80 is not passthrough so the guest can use port 0x80 safely even on
buggy hardware.
4) a buggy chipset is not detected, so io_delay=0x80 and 0x80 is made
passthrough. In principle the guest could crash the machine; however
the host will have written to 0x80 at startup, most likely causing a
crash way before a guest is started. So this should not be a problem
either.
Paolo
next prev parent reply other threads:[~2009-06-22 10:12 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
2009-06-22 10:11 ` Paolo Bonzini [this message]
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=4A3F58EF.8010206@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.