Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,049
    • Issues 3,049
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 993
    • Merge requests 993
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MesaMesa
  • mesamesa
  • Merge requests
  • !12402

[HOLD] panfrost,v3d,asahi,lima,vc4,tegra,etnaviv,freedreno: Don't allocate scanout buffers for PIPE_BIND_SHARED requests

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Roman Stratiienko requested to merge roman.stratiienko/mesa:no-scanout-for-shared into main Aug 17, 2021
  • Overview 42
  • Commits 8
  • Pipelines 8
  • Changes 8
PIPE_BIND_SHARED means that buffer can be shared between processes
using dma-buf fd (or flink name).

Such buffers will not be used by display controllers
(otherwise PIPE_BIND_SCANOUT must be requested additionally).

To allocate them using renderonly mesa3d will use DRM_IOCTL_MODE_CREATE_DUMB
ioctl on display controller DRM node, which use CMA for most of the platforms.

Moreover renderonly will not select best modifier for such allocation
(usually only LINEAR is supported).

Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5237
Edited Aug 31, 2021 by Roman Stratiienko
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: no-scanout-for-shared