| commit | de18a29e0fa3904894b4e02fae0e712cd43f740c | |
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | |
| Sat, 27 Nov 2010 21:30:41 +0000 (27 22:30 +0100) | ||
| committer | Chris Wilson <chris@chris-wilson.co.uk> | |
| Sun, 28 Nov 2010 09:05:12 +0000 (28 09:05 +0000) | ||
| tree | dc12def0252ae2bbd044a2666429fee9955cec37 | treesnapshot (tar.gz zip) |
| parent | ba84cd1f2b5dd49bda9300c5a11373f7e14c3c66 | commitdiff |
drm/i915: fix regression due to ba3d8d749b01548b9
We don't track gpu flush request in any special way. So even with
obj->write_domain == 0, a gpu flush might be outstanding but no
yet executed. Even worse, the latest request might use the object
only for reading. So and unconditional call to object_wait_rendering
is needed for !pipelined.
Hence revert that patch fully and untangle the flushing from the
synchronization again.
Reported-by: Keith Packard <keithp@keithp.com>
Tested-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
We don't track gpu flush request in any special way. So even with
obj->write_domain == 0, a gpu flush might be outstanding but no
yet executed. Even worse, the latest request might use the object
only for reading. So and unconditional call to object_wait_rendering
is needed for !pipelined.
Hence revert that patch fully and untangle the flushing from the
synchronization again.
Reported-by: Keith Packard <keithp@keithp.com>
Tested-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
| drivers/gpu/drm/i915/i915_gem.c | diffblobblamehistory |