From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Check engine->default_state mapping on module load
Date: Fri, 14 Sep 2018 10:43:12 +0100 [thread overview]
Message-ID: <812bbd60-c76c-a5b4-8030-909ea74963d6@linux.intel.com> (raw)
In-Reply-To: <20180914092158.7248-1-chris@chris-wilson.co.uk>
On 14/09/2018 10:21, Chris Wilson wrote:
> Check we can indeed acquire a WB mapping of the context image on module
> load. Later this will give us the opportunity to validate that we can
> switch from WC to WB as required.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index be9d012d851b..37353afec66e 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -5424,6 +5424,7 @@ static int __intel_engines_record_defaults(struct drm_i915_private *i915)
>
> for_each_engine(engine, i915, id) {
> struct i915_vma *state;
> + void *vaddr;
>
> state = to_intel_context(ctx, engine)->state;
> if (!state)
> @@ -5446,6 +5447,16 @@ static int __intel_engines_record_defaults(struct drm_i915_private *i915)
> goto err_active;
>
> engine->default_state = i915_gem_object_get(state->obj);
> +
> + /* Check we can acquire the image of the context state */
> + vaddr = i915_gem_object_pin_map(engine->default_state,
> + I915_MAP_WB);
> + if (IS_ERR(vaddr)) {
> + err = PTR_ERR(vaddr);
> + goto err_active;
> + }
> +
> + i915_gem_object_unpin_map(engine->default_state);
Ah this perhaps strengthens the argument to have
__intel_engines_pin_default_state? (And the unpin pair.)
And I guess you made this patch come before the switch to WC since it is
not FORCE_WB here?
Regards,
Tvrtko
> }
>
> if (IS_ENABLED(CONFIG_DRM_I915_DEBUG_GEM)) {
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-14 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 9:21 [PATCH] drm/i915: Check engine->default_state mapping on module load Chris Wilson
2018-09-14 9:43 ` Tvrtko Ursulin [this message]
2018-09-14 9:51 ` Chris Wilson
2018-09-14 10:03 ` Tvrtko Ursulin
2018-09-14 10:52 ` Chris Wilson
2018-09-14 10:58 ` Tvrtko Ursulin
2018-09-14 11:17 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-09-14 12:55 ` ✓ Fi.CI.IGT: " Patchwork
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=812bbd60-c76c-a5b4-8030-909ea74963d6@linux.intel.com \
--to=tvrtko.ursulin@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;
as well as URLs for NNTP newsgroup(s).