For convenience when debugging user issues show the autotuning
RPS parameters in debugfs/i915_rps_boost_info.
Signed-off-by: Chris Wilson
Cc: Rainer Hochecker
---
drivers/gpu/drm/i915/i915_debugfs.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/gpu
== Series Details ==
Series: drm/i915: Show RPS autotuning thresholds along with waitboost
URL : https://patchwork.freedesktop.org/series/11063/
State : failure
== Summary ==
Series 11063v1 drm/i915: Show RPS autotuning thresholds along with waitboost
http://patchwork.freedesktop.org/api/1.0/s
For convenience when debugging user issues show the autotuning
RPS parameters in debugfs/i915_rps_boost_info.
v2: Refine the presentation
Signed-off-by: Chris Wilson
Cc: frit...@kodi.tv
---
drivers/gpu/drm/i915/i915_debugfs.c | 43 +++--
1 file changed, 41 insert
== Series Details ==
Series: drm/i915: Show RPS autotuning thresholds along with waitboost (rev2)
URL : https://patchwork.freedesktop.org/series/11063/
State : failure
== Summary ==
Series 11063v2 drm/i915: Show RPS autotuning thresholds along with waitboost
http://patchwork.freedesktop.org/ap
-autotuning-thresholds-along-with-waitboost/20160814-213058
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-x009-201633 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
Closed vma are removed from the obj->vma_list so that they cannot be
found by userspace. However, this means that when forcibly unbinding an
object, we have to wait upon all rendering to that object first in order
for the closed, but active, vma to be reaped and their bindings removed.
Reported-by
If the obj->vma_list is empty, we immediately return ret. However, we
are doing so having never set it to any value, it should be zero!
Reported-by: Matthew Auld
References: https://bugs.freedesktop.org/show_bug.cgi?id=97343
Fixes: aa653a685d81 ("drm/i915: Be more careful when unbinding vma")
Sig
Reviewed-by: Matthew Auld
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Reviewed-by: Matthew Auld
Tested-by: Matthew Auld
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signed-off-by: Eric Engestrom
---
I moved the main bits to be the first diffs, shouldn't affect anything
when applying the patch, but I wanted to ask:
I don't like the hard-coded `32` the appears in both kmalloc() and
snprintf(), what do you think? If you don't like it either, what would
you sugg
This week's regressions.
+---+---+++
| BugId | Summary | Created on |
Bisect |
+---+---+++
| 97254 | [SKL] [regression] d
== Series Details ==
Series: series starting with [1/2] drm/i915: Initialize return value for empty
i915_gem_object_unbind()
URL : https://patchwork.freedesktop.org/series/11067/
State : failure
== Summary ==
Applying: drm/i915: Initialize return value for empty i915_gem_object_unbind()
fatal
== Series Details ==
Series: drm: make drm_get_format_name thread-safe
URL : https://patchwork.freedesktop.org/series/11069/
State : failure
== Summary ==
Applying: drm: make drm_get_format_name thread-safe
Using index info to reconstruct a base tree...
M drivers/gpu/drm/drm_crtc.c
M
On Sun, Aug 14, 2016 at 11:01:35PM +0900, Masami Hiramatsu wrote:
> Hello,
>
> I've found a suspicious circular locking dependency in i915 by lockdep.
> It seems main driver initialization thread and sub fbdev configuration
> thread take locks in different order implicitly. Please check it.
>
> T
14 matches
Mail list logo