All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar Valsan, Prathap" <prathap.kumar.valsan@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Do initial mocs configuration directly
Date: Wed, 16 Oct 2019 13:08:18 -0400	[thread overview]
Message-ID: <20191016170818.GA3257@intel.com> (raw)
In-Reply-To: <20191016090749.7092-1-chris@chris-wilson.co.uk>

On Wed, Oct 16, 2019 at 10:07:49AM +0100, Chris Wilson wrote:
> Now that we record the default "goldenstate" context, we do not need to
> emit the mocs registers at the start of each context and can simply do
> mmio before the first context and capture the registers as part of its
> default image. As a consequence, this means that we repeat the mmio
> after each engine reset, fixing up any platform and registers that were
> zapped by the reset (for those platforms with global not context-saved
> settings).
> 
> References: https://bugs.freedesktop.org/show_bug.cgi?id=111723
> References: https://bugs.freedesktop.org/show_bug.cgi?id=111645
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
> ---
>  drivers/gpu/drm/i915/gt/intel_mocs.c | 281 +++++++--------------------
>  drivers/gpu/drm/i915/gt/intel_mocs.h |   3 -
>  drivers/gpu/drm/i915/i915_gem.c      |   9 -
>  3 files changed, 73 insertions(+), 220 deletions(-)
> 
> +/**
> + * intel_mocs_init_engine() - emit the mocs control table
> + * @engine:	The engine for whom to emit the registers.
> + *
> + * This function simply emits a MI_LOAD_REGISTER_IMM command for the
This function description  needs a fix as we don't emit the mocs now.

Reviewed-by: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>


> + * given table starting at the given address.
> + */
> +void intel_mocs_init_engine(struct intel_engine_cs *engine)
>  {
> -- 
> 2.23.0
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-10-16 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  9:07 [PATCH] drm/i915: Do initial mocs configuration directly Chris Wilson
2019-10-16 10:24 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-16 17:08 ` Kumar Valsan, Prathap [this message]
2019-10-16 18:34 ` ✗ Fi.CI.IGT: failure " 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=20191016170818.GA3257@intel.com \
    --to=prathap.kumar.valsan@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 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.