From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Michel Thierry <michel.thierry@intel.com>,
Oscar Mateo <oscar.mateo@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Transform whitelisting WAs into a simple reg write
Date: Fri, 29 Sep 2017 13:25:52 +0300 [thread overview]
Message-ID: <1506680752.4729.41.camel@linux.intel.com> (raw)
In-Reply-To: <0e4a2ecc-1d51-25df-f8eb-6856ceea01d4@intel.com>
On Thu, 2017-09-28 at 16:47 -0700, Michel Thierry wrote:
> On 28/09/17 15:40, Oscar Mateo wrote:
> > RING_FORCE_TO_NONPRIV registers do not live in the logical context. They are simply
> > global privileged MMIO registers that happen to be powercontext saved and restored
> > (meaning only they can survive RC6). Therefore, there is absolutely no need to save
> > them so that they can be restored everytime we create a new logical context.
> >
> > Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_engine_cs.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> > index a28e2a8..a75f5e8 100644
> > --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> > +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> > @@ -845,8 +845,8 @@ static int wa_ring_whitelist_reg(struct intel_engine_cs *engine,
> > if (WARN_ON(index >= RING_MAX_NONPRIV_SLOTS))
> > return -EINVAL;
> >
> > - WA_WRITE(RING_FORCE_TO_NONPRIV(engine->mmio_base, index),
> > - i915_mmio_reg_offset(reg));
> > + I915_WRITE(RING_FORCE_TO_NONPRIV(engine->mmio_base, index),
> > + i915_mmio_reg_offset(reg));
> > wa->hw_whitelist_count[engine->id]++;
> >
> > return 0;
> > --
> > 1.9.1
> >
>
> I see RCS_FORCE_TO_NONPRIV in "Render Engine *Power* Context" and not in
> the "Register State Context", so
>
> Acked-by: Michel Thierry <michel.thierry@intel.com>
You reviewed the spec and the code, so should be Reviewed-by :)
Then this could be merged, too.
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
next prev parent reply other threads:[~2017-09-29 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 22:40 [PATCH] drm/i915: Transform whitelisting WAs into a simple reg write Oscar Mateo
2017-09-28 23:03 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-09-28 23:47 ` [PATCH] " Michel Thierry
2017-09-29 10:25 ` Joonas Lahtinen [this message]
2017-09-29 15:22 ` Michel Thierry
2017-09-29 0:53 ` ✓ Fi.CI.IGT: success for " Patchwork
2017-09-29 8:38 ` [PATCH] " Chris Wilson
2017-10-03 12:51 ` Joonas Lahtinen
2017-10-04 12:39 ` Mika Kuoppala
2017-10-04 13:17 ` Chris Wilson
2017-10-04 20:54 ` Oscar Mateo
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=1506680752.4729.41.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel.thierry@intel.com \
--cc=oscar.mateo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox