From: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
To: Jindrich Makovicka
<makovick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Working on an entry-level project
Date: Wed, 31 Oct 2007 12:18:29 -0600 [thread overview]
Message-ID: <4728C6F5.6010800@cs.ualberta.ca> (raw)
In-Reply-To: <20071015185341.09a732b2@holly>
Jindrich Makovicka wrote:
> On Mon, 15 Oct 2007 08:33:43 -0600
> Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org> wrote:
>
>> Jindrich Makovicka wrote:
>>> On Sat, 13 Oct 2007 12:39:15 +0200
>>>
>>> Even if it doesn't bring any performance benefits, I think that
>>> having a smoothly moving mouse cursor is useful, if you intend to
>>> run a desktop operating system inside QEMU. The current refresh
>>> rate QEMU uses is quite low and the mouse interactivity is poor in
>>> comparison with vmware
>>> + vmware tools.
>>>
>>> I am currently using the attached patch to improve the mouse
>>> interactivity - it shortens the screen refresh interval to 10 ms
>>> when the mouse or keyboard is active, and returns to 30 ms after a
>>> 100 ms inactivity period.
>>>
>> Hi Jindrich,
>>
>> Thanks for posting this. Is there a particular guest that you find
>> best demonstrates this?
>
> IMO any guest that uses the mouse. I use KVM to run WindowsXP,
> where the effect is clearly visible, but it will be the same in XWindow.
Hi Jindrich,
Sorry for the delay in getting on this. I notice your patch stalls the
system when -vnc is used. Do you have any idea why? I'll look into it,
but I thought I should check with you first.
Thanks,
Cam
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-31 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:07 Working on an entry-level project Cam Macdonell
[not found] ` <470CF8B2.4070104-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-10 16:05 ` Izik Eidus
[not found] ` <470CF853.5030502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 16:52 ` Cam Macdonell
[not found] ` <470D0359.5030607-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-11 8:40 ` Dor Laor
[not found] ` <470DE190.7070701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 16:07 ` Cam Macdonell
[not found] ` <470E4A55.807-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-12 10:07 ` Dor Laor
[not found] ` <470F477E.4060302-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-12 19:30 ` Cam Macdonell
[not found] ` <470FCB69.1050105-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-13 10:39 ` Izik Eidus
[not found] ` <4710A053.4030400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-13 21:16 ` Jindrich Makovicka
[not found] ` <47137A47.9010505@cs.ualberta.ca>
[not found] ` <20071015185341.09a732b2@holly>
2007-10-31 18:18 ` Cam Macdonell [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=4728C6F5.6010800@cs.ualberta.ca \
--to=cam-edfdblatwiyxbbii50afww@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=makovick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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