All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Thierry <michel.thierry@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/i915/gtt: Mark newly created ppgtt dirty
Date: Tue, 8 Sep 2015 17:31:05 +0100	[thread overview]
Message-ID: <55EF0D49.6000001@intel.com> (raw)
In-Reply-To: <1441729223-28269-1-git-send-email-mika.kuoppala@intel.com>

On 9/8/2015 5:20 PM, Mika Kuoppala wrote:
> We mark ppgtt dirty when vm area grows. As one needs
> to allocate atleast one batchbuffer object before running
> anything in vm space, this was considered adequate. However in
> init, we run batch which doesn't need to allocate anything. This
> is the render state initialization batch, part of context init.
> Newly created ppgtt is not marked dirty as no allocations for it
> are done. This results bb emission skip the pdps writing to hw,
> and we start the batch with uninitialized (zero) pdp registers
> causing gpu hangs early in the init.

That's true, although I was under the impression that the render state 
batch was executed in the ggtt.
>
> Always mark newly created ppgtts dirty to ensure that pdps are
> pushed before first bb.
>
> Cc: Michel Thierry <michel.thierry@intel.com>
> Cc: Arun Siluvery <arun.siluvery@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
>   drivers/gpu/drm/i915/i915_gem_gtt.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
> index 8786281..41dcfca 100644
> --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
> @@ -2134,6 +2134,8 @@ int i915_ppgtt_init(struct drm_device *dev, struct i915_hw_ppgtt *ppgtt)
>   		i915_init_vm(dev_priv, &ppgtt->base);
>   	}
>
> +	mark_tlbs_dirty(ppgtt);
> +

Does this also apply for gen7? (or should only be in gen8_ppgtt_init).
>   	return ret;
>   }
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-09-08 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 16:20 [PATCH 1/1] drm/i915/gtt: Mark newly created ppgtt dirty Mika Kuoppala
2015-09-08 16:31 ` Michel Thierry [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=55EF0D49.6000001@intel.com \
    --to=michel.thierry@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.intel.com \
    /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.