Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	"Siluvery, Arun" <arun.siluvery@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Wait and retry if there is no space in the aperture mappable area
Date: Tue, 22 Oct 2013 14:30:40 +0200	[thread overview]
Message-ID: <20131022123039.GO4830@phenom.ffwll.local> (raw)
In-Reply-To: <20131022121532.GF6083@nuc-i3427.alporthouse.com>

On Tue, Oct 22, 2013 at 01:15:32PM +0100, Chris Wilson wrote:
> On Tue, Oct 22, 2013 at 12:04:17PM +0000, Siluvery, Arun wrote:
> > From: "Siluvery, Arun" <arun.siluvery@intel.com>
> > 
> > When a mapping is requested and if there is no space the mapping fails
> > and the region is not physically backed. This results in
> > signal 7(SIGBUS), code 2 (BUS_ADRERR) when it is actually accessed.
> > This patch handles this error, continues to wait and retries to find space.
> 
> Eh, no. The line before will remove everything from the aperture that is
> unpinned. Throwing an evict_everything in here breaks reservations, so I
> think you are just papering over a bug.

If we want to fix this for real (i.e. allow userspace to reliably map
stuff, mabye even bigger than the aperture) we need to fall back to
suballocating tile-row aligned strides of the buffer (maybe pick the tile
row multiply in between 1M-2M). Until that's done userspace can't rely on
gtt mmaps relibly working for large buffers. The current heuristics we're
using is half of the mappable space, but that's probably a bit too
optimistic.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-10-22 12:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 12:04 [PATCH] drm/i915: Wait and retry if there is no space in the aperture mappable area Siluvery, Arun
2013-10-22 12:15 ` Chris Wilson
2013-10-22 12:30   ` Daniel Vetter [this message]
2013-10-23  9:44     ` Bloomfield, Jon
2013-10-23  9:55       ` Daniel Vetter
2013-10-23 10:02       ` Chris Wilson
2013-12-05 14:28 ` Daniel Vetter
2013-12-05 15:14   ` Daniel Vetter
2013-12-05 15:14   ` [PATCH] drm/i915: When evicting something fails, try unpinning old contexts and framebuffers Chris Wilson
2013-12-05 15:19     ` Daniel Vetter
2013-12-05 15:25       ` Chris Wilson
     [not found] <20131023131038.GM3011@nuc-i3427.alporthouse.com>
     [not found] ` <AD48BB7FB99B174FBCC69E228F58B3B601544938@IRSMSX103.ger.corp.intel.com>
     [not found]   ` <CAKMK7uE3gZfSGK0eteNLijGzDEJSXH=gRovRsgVaZZVGqOxZkw@mail.gmail.com>
     [not found]     ` <AD48BB7FB99B174FBCC69E228F58B3B601544FDC@IRSMSX103.ger.corp.intel.com>
     [not found]       ` <20131024153253.GB7752@nuc-i3427.alporthouse.com>
     [not found]         ` <AD48BB7FB99B174FBCC69E228F58B3B601547D89@IRSMSX103.ger.corp.intel.com>
     [not found]           ` <20131101112127.GD13837@nuc-i3427.alporthouse.com>
     [not found]             ` <AD48BB7FB99B174FBCC69E228F58B3B601547DC6@IRSMSX103.ger.corp.intel.com>
     [not found]               ` <20131101115122.GA5664@nuc-i3427.alporthouse.com>
     [not found]                 ` <AD48BB7FB99B174FBCC69E228F58B3B601547E34@IRSMSX103.ger.corp.intel.com>
     [not found]                   ` <20131101124740.GB5664@nuc-i3427.alporthouse.com>
2013-11-01 16:56                     ` [PATCH] drm/i915: Wait and retry if there is no space in the aperture mappable area Daniel Vetter
2013-11-01 18:06                       ` Bloomfield, Jon
2013-11-01 18:37                         ` Daniel Vetter
2013-11-02 12:15                       ` Daniel Vetter

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=20131022123039.GO4830@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=arun.siluvery@intel.com \
    --cc=chris@chris-wilson.co.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