From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Force relocations via cpu if we run out of idle aperture
Date: Thu, 06 Oct 2016 15:28:52 +0300 [thread overview]
Message-ID: <1475756932.3089.3.camel@linux.intel.com> (raw)
In-Reply-To: <20161006074137.29202-1-chris@chris-wilson.co.uk>
On to, 2016-10-06 at 08:41 +0100, Chris Wilson wrote:
> If we run out of enough aperture space to fit the entire object, we
> fallback to trying to insert a single page. However, if that also fails,
> we currently fail to userspace with an unexpected ENOSPC. (ENOSPC means
> to userspace that their batch could not be fitted within the GTT.) Prior
> to commit e8cb909ac3ab ("drm/i915: Fallback to single page GTT
> mmappings for relocations") the approach is to fallback to using the
> slow CPU relocation path in case of iomapping failure, and that is the
> behaviour we need to restore.
>
> Fixes: e8cb909ac3ab ("drm/i915: Fallback to single page GTT mmappings...")
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98101
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-10-06 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 7:41 [PATCH] drm/i915: Force relocations via cpu if we run out of idle aperture Chris Wilson
2016-10-06 8:19 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-10-06 12:28 ` Joonas Lahtinen [this message]
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=1475756932.3089.3.camel@linux.intel.com \
--to=joonas.lahtinen@linux.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