RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 703474 - xen-kbdfront - advertise either absolute or relative coordinates
Summary: xen-kbdfront - advertise either absolute or relative coordinates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Igor Mammedov
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-10 13:26 UTC by Igor Mammedov
Modified: 2011-12-06 13:30 UTC (History)
8 users (show)

Fixed In Version: kernel-2.6.32-153.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 13:30:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Input: xen-kbdfront - advertise either absolute or relative coordinates (3.99 KB, patch)
2011-05-10 16:03 UTC, Igor Mammedov
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1530 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Linux 6 kernel security, bug fix and enhancement update 2011-12-06 01:45:35 UTC

Description Igor Mammedov 2011-05-10 13:26:58 UTC
Resync pvops with upstream. Back-port upstream commit 8c3c283:
 Input: xen-kbdfront - advertise either absolute or relative coordinates

    A virtualized display device is usually viewed with the vncviewer
    application, either by 'xm vnc domU' or with vncviewer localhost:port.
    vncviewer and the RFB protocol provides absolute coordinates to the
    virtual display. These coordinates are either passed through to a PV
    guest or converted to relative coordinates for a HVM guest.
    
    A PV guest receives these coordinates and passes them to the kernels
    evdev driver. There it can be picked up by applications such as the
    xorg-input drivers. Using absolute coordinates avoids issues such as
    guest mouse pointer not tracking host mouse pointer due to wrong mouse
    acceleration settings in the guests X display.
    
    Advertise either absolute or relative coordinates to the input system
    and the evdev driver, depending on what dom0 provides. The xorg-input
    driver prefers relative coordinates even if a devices provides both.

and revert commit c36b58e8 to fix regression introduced by 8c3c283:
 Input: xen-kbdfront - fix mouse getting stuck after save/restore

 If driver has been configured for ABS coordinates at start it will get
    XENKBD_TYPE_POS events and then suddenly after restore it'll start getting
    XENKBD_TYPE_MOTION events, that will be dropped later and they won't get
    into user-space.
 Driver on restore should ask xen for request-abs-pointer again if it is
    available. So restore parts that did it before 8c3c283.

Version-Release number of selected component (if applicable):
all rel6  kernels

Comment 2 Igor Mammedov 2011-05-10 16:03:44 UTC
Created attachment 498088 [details]
Input: xen-kbdfront - advertise either absolute or relative coordinates

Comment 3 RHEL Program Management 2011-05-13 15:23:26 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 4 Aristeu Rozanski 2011-05-25 18:57:04 UTC
Patch(es) available on kernel-2.6.32-153.el6

Comment 7 Qin Guan 2011-07-27 08:34:37 UTC
QE want to know the steps to reproduce/verify this bug, as no definite steps mentioned in the bug description. Also did a testing with 6.1 kernel (2.6.32-131.0.1.el6) x86_64 PV guest on 5.7 x86_64 host, no any mouse/keyboard problem found after save/restore.

Comment 8 Igor Mammedov 2011-07-27 11:40:27 UTC
(In reply to comment #7)
> QE want to know the steps to reproduce/verify this bug, as no definite steps
> mentioned in the bug description. Also did a testing with 6.1 kernel
> (2.6.32-131.0.1.el6) x86_64 PV guest on 5.7 x86_64 host, no any mouse/keyboard
> problem found after save/restore.

You won't find a problem in 6.1 because it was introduced upstream/fc15 by the patch:
  Input: xen-kbdfront - advertise either absolute or relative coordinates
which 6.1 doesn't have. And this BZ is pulling in this patch and a fix for save/restore bug  it introduces.

I suppose checking that nothing is broken with this path should be enough, unless you'll be able to find screwed up evdev/X config  configuration which actually use relative coordinates.

Comment 10 errata-xmlrpc 2011-12-06 13:30:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1530.html


Note You need to log in before you can comment on or make changes to this bug.