summaryrefslogtreecommitdiffstats
path: root/Documentation/Intel-IOMMU.txt
diff options
context:
space:
mode:
authorMika Kuoppala <mika.kuoppala@linux.intel.com>2013-08-30 16:19:28 +0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-09-06 17:55:50 +0200
commitbe62acb4cce1389a28296852737e3917d9cc5b25 (patch)
tree7675ef0ebe4cad2d72f1ec94124f73fa97a42472 /Documentation/Intel-IOMMU.txt
parentbf13e81b904a37d94d83dd6c3b53a147719a3ead (diff)
downloadblackbird-op-linux-be62acb4cce1389a28296852737e3917d9cc5b25.tar.gz
blackbird-op-linux-be62acb4cce1389a28296852737e3917d9cc5b25.zip
drm/i915: ban badly behaving contexts
Now when we have mechanism in place to track which context was guilty of hanging the gpu, it is possible to punish for bad behaviour. If context has recently submitted a faulty batchbuffers guilty of gpu hang and submits another batch which hangs gpu in quick succession, ban it permanently. If ctx is banned, no more batchbuffers will be queued for execution. There is no need for global wedge machinery anymore and it would be unwise to wedge the whole gpu if we have multiple hanging batches queued for execution. Instead just ban the guilty ones and carry on. v2: Store guilty ban status bool in gpu_error instead of pointers that might become danling before hang is declared. v3: Use return value for banned status instead of stashing state into gpu_error (Chris Wilson) v4: - rebase on top of fixed hang stats api - add define for ban period - rename commit and improve commit msg v5: - rely context banning instead of wedging the gpu - beautification and fix for ban calculation (Chris) Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'Documentation/Intel-IOMMU.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud