summaryrefslogtreecommitdiff
path: root/drivers/leds/leds-cpcap.c
diff options
context:
space:
mode:
authorMika Kuoppala <mika.kuoppala@linux.intel.com>2018-06-15 13:44:29 +0300
committerJani Nikula <jani.nikula@intel.com>2018-06-19 15:48:16 +0300
commitbc64e05408cafe3668e7460834935ea3f1764f31 (patch)
treeeeaa442c34fbffb3793dc56333deb81ac2690c67 /drivers/leds/leds-cpcap.c
parent4dccc4d517481282e84335c7acbfd7a1481004b8 (diff)
downloadlinux-bc64e05408cafe3668e7460834935ea3f1764f31.tar.xz
drm/i915: Fix context ban and hang accounting for client
If client is smart or lucky enough to create a new context after each hang, our context banning mechanism will never catch up, and as a result of that it will be saved from client banning. This can result in a never ending streak of gpu hangs caused by bad or malicious client, preventing access from other legit gpu clients. Fix this by always incrementing per client ban score if it hangs in short successions regardless of context ban scoring. The exception are non bannable contexts. They remain detached from client ban scoring mechanism. v2: xchg timestamp, tidyup (Chris) v3: comment, bannable & banned together (Chris) Fixes: b083a0870c79 ("drm/i915: Add per client max context ban limit") Cc: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20180615104429.31477-1-mika.kuoppala@linux.intel.com (cherry picked from commit 14921f3cef85b0167a9145e5f29b9dfc3b2a84dc) Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/leds/leds-cpcap.c')
0 files changed, 0 insertions, 0 deletions