Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xserver xserver
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 934
    • Issues 934
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorg
  • xserverxserver
  • Merge requests
  • !126

Merged
Created Feb 22, 2019 by Alan Coopersmith@alancMaintainer

Set IOPL in the input thread on Solaris

  • Overview 0
  • Commits 4
  • Pipelines 2
  • Changes 14

As discussed in https://lists.x.org/archives/xorg-devel/2019-January/057899.html this fixes the X server to work on a Solaris guest inside VMWare by ensuring the input thread has IOPL set, since Solaris tracks IOPL per thread and new threads don't automatically inherit a raised IOPL.

Specifically, it:

  • stops trying to track IOPL status in a global boolean on Solaris, since it's not a global state for the process
  • adds a new ddxInputThread call from os layer into ddx layer, and a new xf86OSInputThreadInit call from common layer into os-support layer
  • uses those calls to ensure the IOPL is set when initializing the input thread on Solaris
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: input-thread-iopl