From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Gerd Hoffmann' <kraxel@redhat.com>,
'Stefano Stabellini' <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Owen Smith <owen.smith@citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH 3/3 v4] xenfb: Add [feature|request]-raw-pointer
Date: Thu, 12 Oct 2017 09:39:16 +0000 [thread overview]
Message-ID: <0941888f3e184161a54e9c4509a1faab@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <1507800365.26812.11.camel@redhat.com>
> -----Original Message-----
> From: Gerd Hoffmann [mailto:kraxel@redhat.com]
> Sent: 12 October 2017 10:26
> To: Paul Durrant <Paul.Durrant@citrix.com>; 'Stefano Stabellini'
> <sstabellini@kernel.org>; Anthony Perard <anthony.perard@citrix.com>
> Cc: qemu-devel@nongnu.org; xen-devel@lists.xenproject.org; Owen Smith
> <owen.smith@citrix.com>
> Subject: Re: [Xen-devel] [PATCH 3/3 v4] xenfb: Add [feature|request]-raw-
> pointer
>
> Hi,
>
> > It's probably OS specific though. I guess the behaviour changed
> > because the OS favours absolute pointing devices over relative ones
> > and how it has two absolute ones to choose from. How it reconciles
> > those, who knows?
>
> Typically hid emulation calls qemu_input_handler_activate() when the
> guest initializes the device, which moves the device to the top of the
> priority list.
>
> Visible effect on a typical guest with ps/2 mouse and usb-tablet is
> that qemu switches from relative mode (mouse) to absolute mode (tablet)
> when the guest loads the usb hid driver.
>
> I suspect pvmouse is doing the same thing. So it may simply depend on
> guest driver load order whenever pvmouse or usb-tablet is used.
>
> Simplest fix is probably to only attach the device you plan to use to
> the guest. If you can't turn off pvmouse for xen guests then you might
> want drop the qemu_input_handler_activate() call, so it behaves simliar
> to the ps/2 mouse (is used in case no other pointer device is present).
Avoiding the activate call sounds reasonable and should avoid the behavioural change.
Cheers,
Paul
>
> HTH,
> Gerd
next prev parent reply other threads:[~2017-10-12 9:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:43 [Qemu-devel] [PATCH 0/3 v4] xenfb: Enablement for Windows PV HID frontend Owen Smith
2017-09-26 14:43 ` [Qemu-devel] [PATCH 1/3 v4] ui/input: add qemu_input_qcode_to_linux Owen Smith
2017-09-26 14:43 ` [Qemu-devel] [PATCH 2/3 v4] xenfb: Use Input Handlers directly Owen Smith
2017-10-02 17:33 ` Anthony PERARD
2017-09-26 14:43 ` [Qemu-devel] [PATCH 3/3 v4] xenfb: Add [feature|request]-raw-pointer Owen Smith
2017-10-02 17:01 ` Anthony PERARD
2017-10-10 23:52 ` Stefano Stabellini
2017-10-11 15:47 ` Anthony PERARD
2017-10-11 20:19 ` Stefano Stabellini
2017-10-12 7:58 ` [Qemu-devel] [Xen-devel] " Paul Durrant
2017-10-12 9:26 ` Gerd Hoffmann
2017-10-12 9:39 ` Paul Durrant [this message]
2017-10-12 17:27 ` Stefano Stabellini
2017-10-19 9:00 ` Owen Smith
2017-10-12 10:38 ` [Qemu-devel] " Anthony PERARD
2017-09-29 10:26 ` [Qemu-devel] [PATCH 0/3 v4] xenfb: Enablement for Windows PV HID frontend Gerd Hoffmann
2017-09-29 10:33 ` Daniel P. Berrange
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=0941888f3e184161a54e9c4509a1faab@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=kraxel@redhat.com \
--cc=owen.smith@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).