From: Erik Rull <erik.rull@rdsoftware.de>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bad USB tablet update rate on qemu-1.0
Date: Thu, 19 Jan 2012 20:15:43 +0100 [thread overview]
Message-ID: <4F186BDF.2050108@rdsoftware.de> (raw)
In-Reply-To: <4F184B6C.9060004@suse.de>
Andreas Färber wrote:
> Am 19.01.2012 17:40, schrieb Erik Rull:
>> Erik Rull wrote:
>>> Erik Rull wrote:
>>>> Erik Rull wrote:
>>>>> Anthony Liguori wrote:
>>>>>> On 12/19/2011 03:33 PM, Erik Rull wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> coming from qemu 0.14 the usbdevice tablet update rate gets really
>>>>>>> bad in
>>>>>>> qemu-1.0 with the same guest.
>>>>>>
>>>>>> What's the specific guest?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Anthony Liguori
>>>>>>
>>>>>
>>>>> It's a Windows XP guest. It was fine in 0.14
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Erik
>>>>>
>>>>
>>>> Any progress here? I tested it on another CPU board there it was worse -
>>>> only 1-2 cursor updates per second :-(
>>>> I tried to use the wacom-tablet but didn't find a driver that works.
>>>>
>>>> Best regards,
>>>>
>>>> Erik
>>>>
>>>
>>> Hi all,
>>>
>>> today I tested some stuff with VNC for remote access of the VM - there
>>> the
>>> update rate of the USB tablet (mouse cursor) was really great. So the
>>> question is now:
>>> - Same host operating system for 0.14 and 1.0
>>> - Same command line parameters beside the vnc option
>>> Why is the native mouse on the qemu 0.14 system good for both vnc and
>>> native and on the qemu 1.0 system only good for vnc and bad for the
>>> native
>>> hardware mouse?
>>>
>>> Maybe this helps finding the source of evil...
>>> If you have ideas what to change / patches to test, just let me know.
>>>
>>> Best regards,
>>>
>>> Erik
>>>
>>
>> Hi all,
>>
>> I additionally tested -std vga to exclude that it might be related to
>> the cirrus emulation - but same result. So there seems to be a
>> difference between the captured cursor for the native X-Windows window
>> and the VNC window that occured somewhere between 0.14 and 1.0.
>
> Then try `git bisect start v1.0 v0.14.0' to find out when exactly the
> perceived behavior changed. :)
>
> Andreas
>
Hi Andreas,
thanks for the hint, I haven't used git up to now. Very interesting feature.
I just did a clone of the current qemu-kvm (which I use) and started to
bisect, but got an error, where I don't know how to proceed:
erik@debian:~/qemu-test/qemu-kvm$ git bisect good qemu-kvm-0.14.0
You need to start by "git bisect start"
Do you want me to do it for you [Y/n]?
erik@debian:~/qemu-test/qemu-kvm$ git bisect bad qemu-kvm-1.0
Bisecting: 2043 revisions left to test after this
fatal: Entry 'roms/seabios' not uptodate. Cannot merge.
erik@debian:~/qemu-test/qemu-kvm$
Any ideas?
I did a git pull, but I just got the response that it is already up to date...
Best regards,
Erik
next prev parent reply other threads:[~2012-01-19 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 21:33 [Qemu-devel] bad USB tablet update rate on qemu-1.0 Erik Rull
2011-12-19 21:48 ` Anthony Liguori
2011-12-19 21:55 ` Erik Rull
2012-01-04 23:17 ` Erik Rull
2012-01-18 21:28 ` Erik Rull
2012-01-18 21:46 ` Erik Rull
2012-01-19 16:40 ` Erik Rull
2012-01-19 16:57 ` Andreas Färber
2012-01-19 19:15 ` Erik Rull [this message]
2012-01-20 9:09 ` Andreas Färber
2012-01-20 12:25 ` Erik Rull
-- strict thread matches above, loose matches on Subject: below --
2012-01-23 8:57 erik.rull
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=4F186BDF.2050108@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=afaerber@suse.de \
--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).