Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
until the the problem with a trashed fb obj during reboot is tracked
down anyway, as this prevents having to fsck continually.
|
|
|
|
|
|
them when appropriate.
|
|
a call to functions that implement the same code sequence.
|
|
Seems to resolve wait_seqno getting into a state where it is
stuck in the gemwt msleep forever.
|
|
|
|
|
|
backport a fix from linux:
The bit controlling whether PIPE_CONTROL DW/QW write targets
the global GTT or PPGTT moved moved from DW 2 bit 2 to
DW 1 bit 24 on IVB.
I verified on IVB that the fix is in fact effective. Without the fix
none of the scratch writes actually landed in the pipe control page.
With the fix the writes show up correctly.
v2: move PIPE_CONTROL_GLOBAL_GTT_IVB setup to where other flags are set
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now we no longer call i915_gem_object_move_to_inactive() on objects that are
not active.
|
|
|
|
to what Linux does.
|
|
|
|
|
|
|
|
|
|
|