Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • drivers
  • gpu
  • drm
  • i915
  • i915_gem_context.c
Find file BlameHistoryPermalink
  • Ben Widawsky's avatar
    drm/i915: possibly invalidate TLB before context switch · 12b0286f
    Ben Widawsky authored Jun 04, 2012
    From http://intellinuxgraphics.org/documentation/SNB/IHD_OS_Vol1_Part3.pdf
    
    
    
    [DevSNB] If Flush TLB invalidation Mode is enabled it's the driver's
    responsibility to invalidate the TLBs at least once after the previous
    context switch after any GTT mappings changed (including new GTT
    entries).  This can be done by a pipelined PIPE_CONTROL with TLB inv bit
    set immediately before MI_SET_CONTEXT.
    
    On GEN7 the invalidation mode is explicitly set, but this appears to be
    lacking for GEN6. Since I don't know the history on this, I've decided
    to dynamically read the value at ring init time, and use that value
    throughout.
    
    v2: better comment (daniel)
    
    Signed-off-by: default avatarBen Widawsky <ben@bwidawsk.net>
    12b0286f