diff options
author | Daniele Ceraolo Spurio <[email protected]> | 2020-02-18 14:33:26 -0800 |
---|---|---|
committer | Chris Wilson <[email protected]> | 2020-02-20 17:48:08 +0000 |
commit | 42f96e5bd41e91fc10f7adbcbf0031742eb56be1 (patch) | |
tree | 35f16efb5db35ddb49af6dad089a3684905b9d25 /lib/test_fortify/write_overflow-strcpy.c | |
parent | 3acffa8cba757a60c0fe24874e0456df8e494778 (diff) |
drm/i915/uc: consolidate firmware cleanup
We are quite trigger happy in cleaning up the firmware blobs, as we do
so from several error/fini paths in GuC/HuC/uC code. We do have the
__uc_cleanup_firmwares cleanup function, which unwinds
__uc_fetch_firmwares and is already called both from the error path of
gem_init and from gem_driver_release, so let's stop cleaning up from
all the other paths.
The fact that we're not cleaning the firmware immediately means that
we can't consider firmware availability as an indication of
initialization success. A "LOADABLE" status has been added to
indicate that the initialization was successful, to be used to
selectively load HuC only if HuC init has completed (HuC init failure
is not considered a fatal error).
v2: s/ready_to_load/loadable (Michal), only run guc/huc_fini if the
fw is in loadable state
Signed-off-by: Daniele Ceraolo Spurio <[email protected]>
Cc: Chris Wilson <[email protected]>
Cc: Michal Wajdeczko <[email protected]>
Reviewed-by: Michal Wajdeczko <[email protected]> #v1
Reviewed-by: John Harrison <[email protected]>
Signed-off-by: Chris Wilson <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strcpy.c')
0 files changed, 0 insertions, 0 deletions