https://bugzilla.novell.com/show_bug.cgi?id=655937
https://bugzilla.novell.com/show_bug.cgi?id=655937#c11
--- Comment #11 from Bjørn Lie 2011-02-07 19:42:01 UTC ---
But Jeff - should we not do as the upstream says and revert the commit in our
kernel for 11.4 then?
Comment #2 From Chris Wilson 2010-12-16 13:38:29
commit de18a29e0fa3904894b4e02fae0e712cd43f740c
Author: Daniel Vetter
Date: Sat Nov 27 22:30:41 2010 +0100
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
Tested-by: Keith Packard
Signed-off-by: Daniel Vetter
Signed-off-by: Chris Wilson
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.