1. 08 Jan, 2019 3 commits
  2. 07 Jan, 2019 4 commits
  3. 06 Jan, 2019 5 commits
  4. 04 Jan, 2019 1 commit
  5. 28 Dec, 2018 11 commits
  6. 27 Dec, 2018 13 commits
  7. 26 Dec, 2018 3 commits
    • Alyssa Rosenzweig's avatar
      Fix regression in -bjellyfish · da7c2388
      Alyssa Rosenzweig authored
    • Eric Anholt's avatar
      gallium/ttn: Fix setup of outputs_written. · 7d7ecfbc
      Eric Anholt authored
      We need a 64-bit value, otherwise we only handle the low 32, and happen to
      sign-extend to claim to write all varying slots if VARYING_SLOT_VAR2 was
      Fixes: 4d0b2c7a ("ttn: Update shader->info as we generate code.")
      Reviewed-by: Rob Clark's avatarRob Clark <robdclark@gmail.com>
    • Alyssa Rosenzweig's avatar
      panfrost: Manage texture memory with pb_slab · 25c3cae3
      Alyssa Rosenzweig authored
      Previously, we allocated a single 256MB slab of texture memory on init,
      never freed anything, and hoped it was enough. This is bad on so many
      This patch uses the pb_slab interface courtesy of AMD to manage texture
      memory. With the new API, we don't allocate any slabs on startup; we
      instead provide a callback for allocating a new slab of memory, which
      we implement with the existing kbase API. Then, we use its methods to
      allocate and free texture memory.
      For real-world motivation, without this patch, running
      sway+es2gears (via Panfrost/llvmpipe respectively) would allocate 50% of
      my memory, and then crash after a short amount of time due to OOM
      conditions. With this patch, the same combination allocates about 30% of
      memory and can run essentially indefinitely, since we're freeing
      resources appropriately.
      Future patches will extend this interface for other parts of the
      cmdstream to further reduce our memory footprint.