qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] paravirtual mouse/tablet
Date: Thu, 13 Jan 2011 18:19:40 +0100	[thread overview]
Message-ID: <4D2F342C.40707@redhat.com> (raw)
In-Reply-To: <4D2F25EA.3020606@redhat.com>

On 01/13/11 17:18, Avi Kivity wrote:
> On 01/13/2011 12:19 PM, Gerd Hoffmann wrote:
>> Hi,
>>
>> Just throwing a quick writeup into the ring to kickstart the design
>> discussion ;)
>>
>>
>> typedef struct qemu_pvtablet_message {
>> uint32_t size; /* whole message size */
>> uint32_t type; /* qemu_pvtablet_type */
>> uint64_t tv_secs;
>> uint64_t tv_usecs;
>
> time relative to what base?

Guess that needs to be refined ;)

Just something relative (if available) should good enougth.  The 
intended purpose is being able to figure how much time passed between 
two events, so one can figure whenever two mouse clicks should be 
considered a double-click or not.  Ideally the timestamps from the 
original mouse event in the vnc/spice client would be passed all the way 
through to the guest.  Didn't check the protocols whenever they actually 
support that, but I think we should have this in the protocol even if 
they don't ...

cheers,
   Gerd

  parent reply	other threads:[~2011-01-13 17:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 10:19 [Qemu-devel] paravirtual mouse/tablet Gerd Hoffmann
2011-01-13 11:01 ` [Qemu-devel] Re: [Spice-devel] " Stefan Hajnoczi
2011-01-13 11:51   ` Gerd Hoffmann
2011-01-13 15:55     ` Anthony Liguori
2011-01-13 17:08       ` Gerd Hoffmann
2011-01-13 20:41         ` Anthony Liguori
2011-01-14  8:49           ` Gerd Hoffmann
2011-01-14 10:48             ` Daniel P. Berrange
2011-01-14 14:14               ` Anthony Liguori
2011-01-14 14:28               ` Alon Levy
2011-01-14 14:52                 ` Daniel P. Berrange
2011-01-14 16:10                   ` [Spice-devel] [Qemu-devel] " Alon Levy
2011-01-13 15:52 ` [Qemu-devel] " Anthony Liguori
2011-01-13 16:14   ` Avi Kivity
2011-01-13 16:39     ` Anthony Liguori
2011-01-13 17:09       ` Paolo Bonzini
2011-01-13 20:38         ` Anthony Liguori
2011-01-13 17:13       ` Alexander Graf
2011-01-13 20:43         ` Anthony Liguori
2011-01-14 11:27         ` Gerd Hoffmann
2011-01-14 14:36           ` Alexander Graf
2011-01-14 14:56             ` [Spice-devel] " Frédéric Grelot
2011-01-14 15:13             ` Gerd Hoffmann
2011-01-14 15:28               ` Alexander Graf
2011-01-14 15:44                 ` Alexander Graf
2011-01-14 16:31                   ` Gerd Hoffmann
2011-01-14 16:42                     ` Alexander Graf
2011-01-17  7:48                       ` Gerd Hoffmann
2011-01-18 19:57                         ` Alexander Graf
2011-01-15 12:07               ` Alon Levy
2011-01-14 15:37             ` Anthony Liguori
2011-01-14 16:26               ` Gerd Hoffmann
2011-01-14 17:02               ` Peter Maydell
2011-01-17  8:14                 ` Gerd Hoffmann
2011-01-13 16:18 ` Avi Kivity
2011-01-13 16:43   ` Anthony Liguori
2011-01-13 17:19   ` Gerd Hoffmann [this message]
2011-01-13 19:21     ` Avi Kivity
2011-01-13 19:55 ` [Qemu-devel] Re: [Spice-devel] " Alon Levy

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=4D2F342C.40707@redhat.com \
    --to=kraxel@redhat.com \
    --cc=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.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).