Lan, Hai would like to recall the message, Q1 RC2 test report for SNB H264
encoding driver.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
The request to test, and report the warnings is still desired.
These address all of Chris' comments from IRC (I think). I tried to put
the reasoning in the code comments, as well as commits; but I'll add it
here for completeness.
Simplify the acquisition of the forcewake lock by removing the
GIT: [Intel-gfx] [PATCH 1/4] drm/i915: proper use of forcewake
GIT: [Intel-gfx] [PATCH 2/4] drm/i915: refcounts for forcewake
GIT: [Intel-gfx] [PATCH 3/4] drm/i915: userspace interface to the forcewake
refcount
GIT: [Intel-gfx] [PATCH 4/4] drm/i915: optional fewer warning patch
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
New refcounting mechanism for forcewake. The idea is to take away the
need to hold struct_mutex for the duration of register reads, and only
need to hold it to get a reference count. A possible benefit would shave
off some time in actually waking the GPU if it's already awake (a couple
of extra
Provide debugfs access to the refcounted forcewake. This allows a
userspace utility to access some of those hard to reach registers on
newer GPUs. The interface is root-only.
The interface is referred to as a forcewake lock. The term lock refers
to the synchronization between software and
The request to test, and report the warnings is still desired.
These address all of Chris' comments from IRC (I think). I tried to put
the reasoning in the code comments, as well as commits; but I'll add it
here for completeness.
Simplify the acquisition of the forcewake lock by removing the
New refcounting mechanism for forcewake. The idea is to take away the
need to hold struct_mutex for the duration of register reads, and only
need to hold it to get a reference count. A possible benefit would shave
off some time in actually waking the GPU if it's already awake (a couple
of extra
This patch will likely produce much fewer warnings, but perhaps hide
some bugs in the driver. Any warnings while using this patch are
extremely likely to cause problems, while warnings without this patch
are also driver bugs, but much less likely to be causing issues. Without
this patch we may
Fedora 15 recently pushed a test update that caused some problems on my
system. The update is basically a single patch file that appears to be
built from several git commits. I would like to test the commits
individually to see which one is causing the problem.
I have cloned
On Sat, Apr 09, 2011 at 11:31:14PM +0100, Chris Wilson wrote:
On Sat, 9 Apr 2011 13:31:22 -0700, Ben Widawsky b...@bwidawsk.net wrote:
+*
+* Intelligent users of the interface may do a force_wake_get() followed
+* by many register reads and writes, knowing that the reference
11 matches
Mail list logo
