From: Erik Rull <erik.rull@rdsoftware.de>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com
Subject: [Qemu-devel] git bisect results (was: Re: bad USB tablet update rate on qemu-1.0)
Date: Tue, 24 Jan 2012 18:24:00 +0100 [thread overview]
Message-ID: <4F1EE930.40002@rdsoftware.de> (raw)
In-Reply-To: <0N3oon-1SLIfp2hzg-00ckUZ@icpu819.kundenserver.de>
Hi all,
I assume that I found a possible source of the bad usbtablet update rate.
I did some git bisectioning but I didn't get a usable result due to too
many merges (or maybe my little knowledge to git), so I proceeded with some
manual bisectioning by manually selecting commits and tested them.
The problem was that the usbtablet update-rate in qemu-kvm-1.0 was really
bad compared to qemu-kvm-0.15.0.
The first commit where the cursor worked but the update rate was bad is
7cb78eec5cdf6e4131613c64cc1a29476f327242
Before this commit the usbtablet didn't work (no grabbing was possible).
But in 0.15.0 it worked. So I continued searching for interesting points
between these versions.
One point was the SDL commit done 2011-08-05 by Jan Kiszka.
There I found changes that affected the -full-screen option.
So I took the version from the commit above and just started with the
-full-screen option.
And everything was fine (qemu-kvm-1.0 as well)! The update rate is very
good with this option.
But I was not able to find the real change that caused the bad update rate.
Jan - is it possible to track down with this information the cause of the
bad update rate? It seems to be related to SDL - the VNC option is working
fine without -full-screen.
I would like to work without the -full-screen option.
Thanks.
Best regards,
Erik
next prev parent reply other threads:[~2012-01-24 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 8:57 [Qemu-devel] bad USB tablet update rate on qemu-1.0 erik.rull
2012-01-24 17:24 ` Erik Rull [this message]
2012-01-24 18:19 ` [Qemu-devel] git bisect results Jan Kiszka
2012-01-24 18:55 ` Erik Rull
2012-01-24 20:15 ` 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=4F1EE930.40002@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=jan.kiszka@siemens.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).