Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,083
    • Issues 3,083
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1,000
    • Merge requests 1,000
  • 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

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • MesaMesa
  • mesamesa
  • Repository
Switch branch/tag
  • mesa
  • src
  • broadcom
  • vulkan
  • v3dv_cl.c
Find file BlameHistoryPermalink
  • Iago Toral's avatar
    v3dv: ensure we allocate at least the requested space for a CL · a81063d2
    Iago Toral authored Jan 24, 2023 and Marge Bot's avatar Marge Bot committed Jan 24, 2023
    While we are already ensuring we allocate at least 8192 bytes should
    this not be the first allocation and our allocations are typically just
    a few bytes, multilayered framebuffers with large numbers of layers may
    require more space than that in a single allocation.
    
    Fixes: 33259506
    
     ('v3dv: increase BO allocation size when growing CLs')
    Reviewed-by: Eric Engestrom's avatarEric Engestrom <eric@igalia.com>
    Part-of: <!20871>
    a81063d2