summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2012-06-19 20:24:33 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2012-06-19 20:55:18 +0100
commit8141e290b1ac7c4d1524bb389a84a8f375df4634 (patch)
tree0f6b654d032da304a4b878d2fb9eef32f573c2e7
parenteb1d07624e5aeb7b5db7ceb46975091e92185d63 (diff)
sna: Explain why we ignore the busy status result during kgem_bo_flush()
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-rw-r--r--src/sna/kgem.h7
1 files changed, 5 insertions, 2 deletions
diff --git a/src/sna/kgem.h b/src/sna/kgem.h
index 40730c7f..0ab8033f 100644
--- a/src/sna/kgem.h
+++ b/src/sna/kgem.h
@@ -275,8 +275,11 @@ static inline void kgem_bo_flush(struct kgem *kgem, struct kgem_bo *bo)
if (!bo->needs_flush)
return;
- __kgem_flush(kgem, bo);
-
+ /* If the kernel fails to emit the flush, then it will be forced when
+ * we assume direct access. And as the useual failure is EIO, we do
+ * not actualy care.
+ */
+ (void)__kgem_flush(kgem, bo);
bo->needs_flush = false;
}