On 2010.11.04 13:50:24 +0800, Zhenyu Wang wrote:
> On 2010.11.04 02:23:46 +, Chris Wilson wrote:
> > On Tue, 2 Nov 2010 14:24:22 +0800, Zhenyu Wang
> > wrote:
> > > I don't think transcoder bpc setting should matter, but sorry that I'm
> > > short
> > > of time to track down which one extra
On Thu, 2010-11-04 at 11:44 +0800, Liu, Yuanhan wrote:
One should do this 'echo mmiotrace > /sys/kernel/debug/tracing' to enable
> mmio trace.
>
Oops, an error, it's
$ echo mmiotrace >/sys/kernel/debug/tracing/current_tracer
Thanks.
___
Intel-gfx ma
On Tue, 2010-11-02 at 22:55 +0800, Liu Aleaxander wrote:
>
> > Being able to trace the register writes using ftrace is good... In fact we
> > can remove our own printks and just use mmiotrace. So is it possible to
> > post-process mmiotrace into .aub?
>
> As I found mmiotrace can handle the opera
On Tue, 2 Nov 2010 14:24:22 +0800, Zhenyu Wang wrote:
> I don't think transcoder bpc setting should matter, but sorry that I'm short
> of time to track down which one extra read made the difference, my sandybridge
> laptop normally refuse to boot on first time.. ;)
>
> The code operation is same
On Wed, 3 Nov 2010 16:27:57 -0400, Kyle McMartin wrote:
> From: Kyle McMartin
>
> Fixes issue where i915_gfx_val was reporting values several
> orders of magnitude higher than physically possible (without
> leaving scorch marks on my thighs at least.)
Applied to -fixes, thanks.
-Chris
--
Chri
On Wed, 3 Nov 2010 13:31:58 -0500, "Jason Detring"
wrote:
> App running for 60 minutes (we've just started swapping):
>
> /sys/kernel/debug/dri/0/i915_gem_objects
> 514 objects
> 390938624 object bytes
> 3 pinned
> 7471104 pin bytes
> 12 mappable objects in gtt
> 10108928 mappable gtt bytes
> 12
On Wed, 3 Nov 2010 10:26:11 -0500, "Jason Detring"
wrote:
> The problem observed is that performing this switch seems to grow system
> cache usage by about 1.5 to 2 MB per iteration. This is unbounded, and
> will fill both free memory and swap in the course of a few hours when
> running our app
Hello list,
I am seeing a curious memory leak with the Intel X11 driver stack,
specifically the 3D rendering components.
Our application draws a landscape as a series of tiles (i.e. textures
applied to sections of 3D terrain). This application has other non-3D
modes, and the user is allowed to s
