Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: Regression since 53984635a659e360f206a81ada4ae813152d72f1 (drm/i915: use the complete gtt)
Date: Tue, 09 Nov 2010 18:49:34 +0000	[thread overview]
Message-ID: <1289328574.2356.1.camel@pcjc2lap> (raw)
In-Reply-To: <1289326968.2289.4.camel@pcjc2lap>

On Tue, 2010-11-09 at 18:22 +0000, Peter Clifton wrote:
> commit 53984635a659e360f206a81ada4ae813152d72f1
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Wed Sep 22 23:44:24 2010 +0200
> 
>     drm/i915: use the complete gtt
>     
>     At least the part that's currently enabled by the BIOS.
>     
>     Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> 
> Since the above commit, my GL app will crash after a period of sustained
> graphics activity. It appears to use quite a lot of small BOs for
> uploading changed VBO data with glBufferSubData, and I don't think these
> are being purged until the GTT is full.

I can also work around the crash by ensuring nothing gets into unmapable
areas:

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 7c91bf2..d014cd6 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -3538,6 +3538,7 @@ i915_gem_execbuffer_pin(struct drm_device *dev,
                        /* g33/pnv can't fence buffers in the unmappable part */
                        bool need_mappable =
                                entry->relocation_count ? true : need_fence;
+                       need_mappable = true;
 
                        /* Check fence reg constraints and rebind if necessary */
                        if (need_mappable && !obj->map_and_fenceable) {

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

  reply	other threads:[~2010-11-09 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 18:22 Regression since 53984635a659e360f206a81ada4ae813152d72f1 (drm/i915: use the complete gtt) Peter Clifton
2010-11-09 18:49 ` Peter Clifton [this message]
2010-11-09 18:56 ` Chris Wilson
2010-11-09 19:09   ` Peter Clifton
2010-11-09 19:43     ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1289328574.2356.1.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox