We have to do this manually. Somebody had a Great Idea.
I've measured speed-ups just a few percent above the noise level
(below 5% for the best case), but no slowdows. Chris Wilson measured
quite a bit more (10-20% above the usual snb variance) on a more
recent and better tuned version of sna,
-Original Message-
From: Chris Wilson [mailto:ch...@chris-wilson.co.uk]
Sent: Thursday, February 02, 2012 4:52 PM
To: zhigang.g...@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org; zhigang.g...@linux.intel.com
Subject: Re: [PATCH] uxa/glamor: Use a macro to specify module name.
-Original Message-
From: zhigang.g...@linux.intel.com [mailto:zhigang.g...@linux.intel.com]
Sent: Wednesday, February 01, 2012 7:47 PM
To: ch...@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org; zhigang.g...@linux.intel.com
Subject: [PATCH] uxa/glamor: Refine CloseScreen and
This allows to hopefully find out who was responsible for the GPU death.
To simplify post-portem analysis, we also search for the the processes
names when gathering the i915_error_state and when peeking at the list of
active gem objects in debugfs.
Signed-off-by: Eugeni Dodonov
On Thu, Feb 02, 2012 at 02:52:22PM -0200, Eugeni Dodonov wrote:
This allows to hopefully find out who was responsible for the GPU death.
To simplify post-portem analysis, we also search for the the processes
names when gathering the i915_error_state and when peeking at the list of
active gem
width, height parameter of glTexImage2D() includes: texture image
width + 2 * border (if any). So when doing the texture size check
in _mesa_test_proxy_teximage() width and height should not exceed
maximum supported size for target texture type.
i.e. 1 (ctx-Const.MaxTextureLevels
