From: Avi Kivity <avi@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: QEMU-KVM and video performance
Date: Wed, 21 Apr 2010 23:56:57 +0300 [thread overview]
Message-ID: <4BCF6699.2060201@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004212039460.20263@bbs.intern>
On 04/21/2010 09:50 PM, Gerhard Wiesinger wrote:
>>> I don't think changing VGA window is a problem because there are
>>> 500.000-1Mio changes/s possible.
>>
>> 1MB/s, 500k-1M changes/s.... Coincidence? Is it taking a page fault
>> or trap on every write?
>
>
> To clarify:
> Memory Performance writing to segmen A000 is about 1MB/st.
That indicates a fault every write (assuming 8-16 bit writes). If
you're using 256 color vga and not switching banks, this indicates a bug.
> Calling INT 10 set/get window function with different windows (e.g.
> toggling between window page 0 and 1) is about 500.000 to 1Mio
> function calls per second.
That's suprisingly fast. I'd expect 100-200k/sec.
Please run kvm_stat and report output for both tests to confirm.
>
> To get real good VGA performance both parameters should be:
> About >50MB/s for writes to segment A000
> ~500.000 bank switches per second.
First should be doable easily, second is borderline.
> I think this is very easy to distingish:
> 1.) VGA Segment A000 is legacy and should be handled through QEMU and
> not through KVM (because it is much more faster). Also 16 color modes
> should be fast enough there.
> 2.) All other flat PCI memory accesses should be handled through KVM
> (there is a specialized driver loaded for that PCI device in the non
> legacy OS).
>
> Is that easily possible?
No. Code can run in either qemu or kvm, not both. You can switch
between them based on access statistics (early versions of qemu-kvm did
that, without the statistics part), but this isn't trivial.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-04-21 20:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 19:14 [Qemu-devel] QEMU-KVM and video performance Gerhard Wiesinger
2010-04-21 8:59 ` [Qemu-devel] " Avi Kivity
2010-04-21 10:08 ` Jamie Lokier
2010-04-21 10:49 ` Avi Kivity
2010-04-21 18:14 ` Gerhard Wiesinger
2010-04-21 20:49 ` Avi Kivity
2010-04-22 5:37 ` Gerhard Wiesinger
2010-04-22 6:57 ` Avi Kivity
2010-04-21 18:39 ` Jamie Lokier
2010-04-21 20:51 ` Avi Kivity
2010-04-21 21:19 ` Jamie Lokier
2010-04-22 5:44 ` Gerhard Wiesinger
2010-05-12 10:34 ` Jamie Lokier
2010-04-21 18:09 ` Gerhard Wiesinger
2010-04-21 18:33 ` Jamie Lokier
2010-04-21 18:50 ` Gerhard Wiesinger
2010-04-21 18:53 ` Jamie Lokier
2010-04-21 19:08 ` Gerhard Wiesinger
2010-04-21 21:30 ` Jamie Lokier
2010-04-22 6:12 ` Gerhard Wiesinger
2010-05-12 10:23 ` Jamie Lokier
2010-04-21 20:56 ` Avi Kivity [this message]
2010-04-22 6:04 ` Gerhard Wiesinger
2010-04-22 7:03 ` Avi Kivity
2010-05-09 19:35 ` Gerhard Wiesinger
2010-05-10 7:32 ` Avi Kivity
2010-05-12 6:14 ` Gerhard Wiesinger
2010-05-12 6:39 ` Avi Kivity
2011-02-18 7:32 ` [Qemu-devel] Re: QEMU-KVM and video performance - Update Gerhard Wiesinger
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=4BCF6699.2060201@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lists@wiesinger.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).