From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Akash Goel <akash.goel@intel.com>,
"# v4 . 9-rc1+" <drm-intel-fixes@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Limit Valleyview and earlier to only using mappable scanout
Date: Fri, 4 Nov 2016 12:59:08 +0000 [thread overview]
Message-ID: <3a01e78e-5c02-a024-c0ef-e192fc1d567b@linux.intel.com> (raw)
In-Reply-To: <20161104110838.3279-1-chris@chris-wilson.co.uk>
On 04/11/2016 11:08, Chris Wilson wrote:
> Valleyview and Cherryview are definitely limited to only scanning out
> from the first 256MiB and 512MiB of the Global GTT respectively. Lets
> presume that this behaviour was inherited from the display block copied
> from g4x (not Ironlake) and all earlier generations are similarly
> affected. For simplicity, impose that these platforms must scanout from
> the mappable region.
>
> Reported-by: Luis Botello <luis.botello.ortega@intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98036
> Fixes: 2efb813d5388 ("drm/i915: Fallback to using unmappable memory for scanout")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Akash Goel <akash.goel@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: <drm-intel-fixes@lists.freedesktop.org> # v4.9-rc1+
> ---
> This leaves Ironlake -> Haswell with a bit of uncertainity. It is also
> not clear if the scanout accessible region is similarly limited on all
> gen8+, and so whether we need to similarly curtain the upper range for
> their scanouts.
> ---
> drivers/gpu/drm/i915/i915_gem.c | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 269e2487c104..408875fbec66 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -3661,8 +3661,22 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,
> if (view->type == I915_GGTT_VIEW_NORMAL)
> vma = i915_gem_object_ggtt_pin(obj, view, 0, alignment,
> PIN_MAPPABLE | PIN_NONBLOCK);
> - if (IS_ERR(vma))
> - vma = i915_gem_object_ggtt_pin(obj, view, 0, alignment, 0);
> + if (IS_ERR(vma)) {
> + struct drm_i915_private *i915 = to_i915(obj->base.dev);
dev_priv ?
What do we do with i915_params being a global i915?
Regards,
Tvrtko
> + unsigned int flags;
> +
> + /* Valleyview and Cherryview are definitely limited to scanning
> + * out the first 256MiB and 512MiB respectively. Lets presume
> + * this behaviour was inherited from their g4x display engine
> + * and that all earlier gen are similarly limited.
> + */
> + flags = 0;
> + if (INTEL_GEN(i915) < 5 ||
> + IS_VALLEYVIEW(i915) ||
> + IS_CHERRYVIEW(i915))
> + flags = PIN_MAPPABLE;
> + vma = i915_gem_object_ggtt_pin(obj, view, 0, alignment, flags);
> + }
> if (IS_ERR(vma))
> goto err_unpin_display;
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-04 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 11:08 [PATCH] drm/i915: Limit Valleyview and earlier to only using mappable scanout Chris Wilson
2016-11-04 11:29 ` Jani Nikula
2016-11-04 11:41 ` Chris Wilson
2016-11-04 11:45 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-11-04 12:59 ` Tvrtko Ursulin [this message]
2016-11-04 13:06 ` [PATCH] " Chris Wilson
2016-11-04 14:17 ` Jani Nikula
2016-11-07 10:27 ` Ville Syrjälä
2016-11-07 11:00 ` [PATCH v3] " Chris Wilson
2016-11-07 11:01 ` [PATCH v4] " Chris Wilson
2016-11-07 11:36 ` Ville Syrjälä
2016-11-07 12:28 ` 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=3a01e78e-5c02-a024-c0ef-e192fc1d567b@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=akash.goel@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=drm-intel-fixes@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.