From: Gerhard Wiesinger <lists@wiesinger.com>
To: Avi Kivity <avi@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] Re: QEMU-KVM and video performance - Update
Date: Fri, 18 Feb 2011 08:32:17 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1102180822460.32103@bbs.intern> (raw)
In-Reply-To: <4BEA4D36.3020608@redhat.com>
Hello,
Some update on this issue, archive:
http://www.mail-archive.com/kvm@vger.kernel.org/msg32600.html
Seems to be that cirrus VGA is now ok (>1000MB/s up to 2000MB/s). But
cirrus has only 320x200x256colors (Mode 13h) mode implemented in VESA
BIOS.
VMWare and std VGA still have the performance issue.
I guess improvement is related to the following commit:
http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=0d14905b5eb8aa1c2e195e13478bb7c74e1776db
Especially i guess the change in hw/cirrus_vga.c.
Any idea how to fix:
1.) More VESA modes in cirrus VGA (is VESA emulation done by Seabios or by
KVM cirrus BIOS?)
2.) fix in VMWare and std VGA modes the performance, too
Versions are latest dev versions of KVM user part and Seabios from GIT.
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Wed, 12 May 2010, Avi Kivity wrote:
> On 05/12/2010 09:14 AM, Gerhard Wiesinger wrote:
>> On Mon, 10 May 2010, Avi Kivity wrote:
>>
>>> On 05/09/2010 10:35 PM, Gerhard Wiesinger wrote:
>>>>>>
>>>
>>> For 256 color more the first priority is to find out why direct mapping is
>>> not used. I'd suggest tracing the code that makes this decision (in
>>> hw/*vga.c) and seeing if it's right or not.
>>
>> I think this is because A000 is not initialized for KVM (see log below and
>> logging patch attached).
>
> Why isn't it initialized?
>
> Did the guest configure things such as it is impossible to map it directly?
> Or does the configuration allow direct mapping and qemu incorrectly decides
> that it cannot direct map?
>
> Best would be to print out all the configuration registers and interpret them
> according to the specification.
>
>
>>
>> vga_dirty_log_start
>> vga_dirty_log_start_mapping_lfb_vram_mapped, start=0x000A0000,
>> len=0x00008000
>> BUG: kvm_dirty_pages_log_change: invalid parameters
>> 00000000000a0000-00000000000a7fff
>
> Why does this happen?
>
> --
> Do not meddle in the internals of kernels, for they are subtle and quick to
> panic.
>
>
>
prev parent reply other threads:[~2011-02-18 7:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 19:14 QEMU-KVM and video performance Gerhard Wiesinger
2010-04-21 8:59 ` Avi Kivity
2010-04-21 10:08 ` [Qemu-devel] " Jamie Lokier
2010-04-21 10:49 ` Avi Kivity
2010-04-21 18:14 ` Gerhard Wiesinger
2010-04-21 20:49 ` [Qemu-devel] " 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
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 ` [Qemu-devel] " Avi Kivity
2011-02-18 7:32 ` Gerhard Wiesinger [this message]
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=alpine.LFD.2.02.1102180822460.32103@bbs.intern \
--to=lists@wiesinger.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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