summaryrefslogtreecommitdiffstats
path: root/drivers/input/mouse/Makefile
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2010-02-18 10:24:56 +0000
committerEric Anholt <eric@anholt.net>2010-02-22 12:01:39 -0500
commit9df30794f609d9412f14cfd0eb7b45dd64d0b14e (patch)
tree17e2658af3fe1af83c6a89ca13c3c93752bdfd13 /drivers/input/mouse/Makefile
parent7b9c5abee98c54f85bcc04bd4d7ec8d5094c73f4 (diff)
downloadblackbird-op-linux-9df30794f609d9412f14cfd0eb7b45dd64d0b14e.tar.gz
blackbird-op-linux-9df30794f609d9412f14cfd0eb7b45dd64d0b14e.zip
drm/i915: Record batch buffer following GPU error
In order to improve our diagnostic capabilities following a GPU hang and subsequent reset, we need to record the batch buffer that triggered the error. We assume that the current batch buffer, plus a few details about what else is on the active list, will be sufficient -- at the very least an improvement over nothing. The extra information is stored in /debug/dri/.../i915_error_state following an error, and may be decoded using intel_gpu_tools/tools/intel_error_decode. v2: Avoid excessive work under spinlocks. v3: Include ringbuffer for later analysis. v4: Use kunmap correctly and record more buffer state. v5: Search ringbuffer for current batch buffer v6: Use a work fn for the impossible IRQ error case. v7: Avoid non-atomic paths whilst in IRQ context. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Eric Anholt <eric@anholt.net>
Diffstat (limited to 'drivers/input/mouse/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud