qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm: flush the dirty log when unregistering a slot
Date: Fri, 27 Jan 2012 07:50:10 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1201270744500.7498@bbs.intern> (raw)
In-Reply-To: <4F21473B.2000703@redhat.com>

On Thu, 26 Jan 2012, Avi Kivity wrote:

> On 01/25/2012 10:15 PM, Gerhard Wiesinger wrote:
>> On Sun, 15 Jan 2012, Avi Kivity wrote:
>>
>>> On 01/15/2012 04:40 PM, Gerhard Wiesinger wrote:
>>>> On Sun, 15 Jan 2012, Jan Kiszka wrote:
>>>>
>>>>> On 2012-01-15 15:17, Avi Kivity wrote:
>>>>>> Otherwise, the dirty log information is lost in the kernel forever.
>>>>>>
>>>>>> Fixes opensuse-12.1 boot screen, which changes the vga windows
>>>>>> rapidly.
>>>>>
>>>>> Confirmed, problems solved here.
>>>>
>>>> Problem from:
>>>> http://permalink.gmane.org/gmane.comp.emulators.qemu/131853
>>>>
>>>> Confirmed to be fixed, too. Long awaited patch :-)
>>>
>>> Sorry, I forgot about that.  Please ping me if I do that.
>>>
>>>>
>>>> BTW: There is also a major difference in video performance:
>>>> 1.) With Patch: 1400MB/s (MByte/s)
>>>> 2.) Without Patch: 6MB/s
>>>>
>>>> Any reason for that?
>>>
>>> What are you measuring exactly?
>>
>> I'm measuring VGA video performance under DOS with own written test
>> program.
>>
>> What's strange, new findings: Measurement doesn't depend on the patch.
>> Sometimes it is high sometimes low. I think I have to investigate
>> further.
>>
>> Any ideas?
>
> What vga mode are you using?  What does the test program do?

DOS Test programs, source and binaries can be found at:
http://www.wiesinger.com/opensource/qemu/

1.) Measures page A000:0000 with videomode 4F02, see:
http://www.wiesinger.com/opensource/qemu/memperf.c

2.) Second test program measures setting and getting video bank, see:
http://www.wiesinger.com/opensource/qemu/int10per.c
We already talked about the low performance some time ago and tracked it 
down to kernel <=> userspace switching. But I benchmarked it already once 
and I think there are some optimizations possible (linear list search) 
with mapping functions (e.g. trivial hash function before)

Thnx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

  reply	other threads:[~2012-01-27  6:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 14:17 [Qemu-devel] [PATCH] kvm: flush the dirty log when unregistering a slot Avi Kivity
2012-01-15 14:26 ` Jan Kiszka
2012-01-15 14:40   ` Gerhard Wiesinger
2012-01-15 17:01     ` Avi Kivity
2012-01-25 20:15       ` Gerhard Wiesinger
2012-01-26 12:29         ` Avi Kivity
2012-01-27  6:50           ` Gerhard Wiesinger [this message]
2012-01-29 10:15             ` Avi Kivity
2012-01-17 11:25 ` Marcelo Tosatti
2012-01-17 12:28   ` Jan Kiszka

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.1201270744500.7498@bbs.intern \
    --to=lists@wiesinger.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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).