Skip to content
Snippets Groups Projects
Select Git revision
  • fa812ce96a46efc27cae4dcad866aaee9cb25d28
  • vme-testing default
  • ci-test
  • master
  • remoteproc
  • am625-sk-ov5640
  • pcal6534-upstreaming
  • lps22df-upstreaming
  • msc-upstreaming
  • imx8mp
  • iio/noa1305
  • vme-next
  • vme-next-4.14-rc4
  • v4.14-rc4
  • v4.14-rc3
  • v4.14-rc2
  • v4.14-rc1
  • v4.13
  • vme-next-4.13-rc7
  • v4.13-rc7
  • v4.13-rc6
  • v4.13-rc5
  • v4.13-rc4
  • v4.13-rc3
  • v4.13-rc2
  • v4.13-rc1
  • v4.12
  • v4.12-rc7
  • v4.12-rc6
  • v4.12-rc5
  • v4.12-rc4
  • v4.12-rc3
32 results

linux

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Chris Wilson authored
    In switching to using objects for our ppGTT scratch pages, care was not
    taken to avoid trying to unref NULL objects on failure. And for gen6
    ppGTT, it appears we forgot entirely to unwind after a partial allocation
    failure.
    
    Fixes: 89351925 ("drm/i915/gt: Switch to object allocations for page directories")
    Signed-off-by: default avatarChris Wilson <chris@chris-wilson.co.uk>
    Cc: Matthew Auld <matthew.auld@intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Reviewed-by: default avatarMatthew Auld <matthew.auld@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20201019083444.1286-1-chris@chris-wilson.co.uk
    fa812ce9
    History
    Name Last commit Last update