xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Stefano Stabellini' <sstabellini@kernel.org>,
	Anthony Perard <anthony.perard@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Owen Smith <owen.smith@citrix.com>
Subject: Re: [PATCH 3/3 v4] xenfb: Add	[feature|request]-raw-pointer
Date: Thu, 12 Oct 2017 07:58:50 +0000	[thread overview]
Message-ID: <e25a3501923944fbad8e3a560c5cf8f3@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1710111309400.3105@sstabellini-ThinkPad-X260>

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> Stefano Stabellini
> Sent: 11 October 2017 21:19
> To: Anthony Perard <anthony.perard@citrix.com>
> Cc: qemu-devel@nongnu.org; xen-devel@lists.xenproject.org; Stefano
> Stabellini <sstabellini@kernel.org>; Owen Smith <owen.smith@citrix.com>;
> kraxel@redhat.com
> Subject: Re: [Xen-devel] [PATCH 3/3 v4] xenfb: Add [feature|request]-raw-
> pointer
> 
> On Wed, 11 Oct 2017, Anthony PERARD wrote:
> > On Tue, Oct 10, 2017 at 04:52:48PM -0700, Stefano Stabellini wrote:
> > > On Mon, 2 Oct 2017, Anthony PERARD wrote:
> > > > On Tue, Sep 26, 2017 at 02:43:39PM +0000, Owen Smith wrote:
> > > > > Writes "feature-raw-pointer" during init to indicate the backend
> > > > > can pass raw unscaled values for absolute axes to the frontend.
> > > > > Frontends set "request-raw-pointer" to indicate the backend should
> > > > > not attempt to scale absolute values to console size.
> > > > > "request-raw-pointer" is only valid if "request-abs-pointer" is
> > > > > also set. Raw unscaled pointer values are in the range [0, 0x7fff]
> > > > >
> > > > > Signed-off-by: Owen Smith <owen.smith@citrix.com>
> > > >
> > > > Hi Owen,
> > > >
> > > > Why did you remove the following from the commit description?
> > > > > "feature-raw-pointer" and "request-raw-pointer" added to Xen
> > > > > header in commit 7868654ff7fe5e4a2eeae2b277644fa884a5031e
> > > >
> > > > I think that with it, you could have kept stefano's reviewed-by tag.
> > >
> > > Hi Anthony,
> > >
> > > Have you tested this series with a few of different guests? Do you
> > > consider it safe to merge? If so, we can send it upstream (either via
> > > xen or via ui as Gerd kindly offered).
> >
> > Yes, I think it's fine.
> >
> > The only observation I have is that on a Linux guest, when I have
> > usbdevice=tablet, with this series the pv mouse seems to become the
> > primary way of gueting mouse events (without, the tablet is primary).
> > So, on my VNC client instead of having both mouse in the guest and on my
> > desktop being at the same place, there is like a zoom of the mouse (the
> > zoom centered on the top-left corner). (That's better than relative
> > mouse event that we can get with the emulation.)
> 
> Thanks for testing. I am not completely sure about what should be the
> right behavior when both usbdevice=tablet and pvmouse are present.
> Typically, PV devices take precedence over emulated devices, so maybe
> it is OK that PV mouse is the primary device in this case.
> 
> But we would need to document this behavioral change in the commit
> descriptions.
> 

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?

  Paul

> The other question is whether the "zoom of the mouse" you are seeing is
> normal or whether we can "fix" it somehow. I guess it has always been
> the case for PV mouse? It is not something new, is it?
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-10-12  8:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 14:43 [PATCH 0/3 v4] xenfb: Enablement for Windows PV HID frontend Owen Smith
2017-09-26 14:43 ` [PATCH 1/3 v4] ui/input: add qemu_input_qcode_to_linux Owen Smith
2017-09-26 14:43 ` [PATCH 2/3 v4] xenfb: Use Input Handlers directly Owen Smith
2017-10-02 17:33   ` Anthony PERARD
2017-09-26 14:43 ` [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           ` Paul Durrant [this message]
2017-10-12  9:26             ` Gerd Hoffmann
2017-10-12  9:39               ` Paul Durrant
2017-10-12 17:27                 ` Stefano Stabellini
2017-10-19  9:00                   ` Owen Smith
2017-10-12 10:38           ` Anthony PERARD
2017-09-29 10:26 ` [PATCH 0/3 v4] xenfb: Enablement for Windows PV HID frontend Gerd Hoffmann
2017-09-29 10:33   ` [Qemu-devel] " 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=e25a3501923944fbad8e3a560c5cf8f3@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).