diff options
| author |   Chris Wilson <chris@chris-wilson.co.uk> | 2017-12-13 13:43:47 +0000 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2017-12-13 18:53:35 +0000 |
| commit | 6ca9a2beb54a385c8cc5e39a9d2ef49945896c64 (patch) | |
| tree | d50c2b914ece7713444ecdae37903b9c622ec8dc /drivers/gpu/drm/i915/intel_guc.c | |
| parent | drm/i915: Ratelimit request allocation under oom (diff) | |
| download | linux-dev-6ca9a2beb54a385c8cc5e39a9d2ef49945896c64.tar.xz linux-dev-6ca9a2beb54a385c8cc5e39a9d2ef49945896c64.zip | |
drm/i915: Unwind i915_gem_init() failure
Since Michal introduced new user controllable errors other than -EIO
during i915_gem_init(), we need to actually unwind on the error path as
we have to abort the module load (and we expect to do so cleanly!).
As we now teardown key state and then mark the driver as wedged (on
EIO), we have to be careful to not allow ourselves to resume and
unwedge, thus attempting to use the uninitialised driver.
v2: Try not to free driver state for the suppressed EIO
v3: Use load-fault-injection to test both error/recovery paths.
References: 8620eb1dbbf2 ("drm/i915/uc: Don't use -EIO to report missing firmware")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171213134347.4608-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_guc.c')
0 files changed, 0 insertions, 0 deletions