From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Transform whitelisting WAs into a simple reg write
Date: Tue, 03 Oct 2017 15:51:58 +0300 [thread overview]
Message-ID: <1507035118.4728.58.camel@linux.intel.com> (raw)
In-Reply-To: <150667431011.27384.7045201545700621629@mail.alporthouse.com>
On Fri, 2017-09-29 at 09:38 +0100, Chris Wilson wrote:
> Quoting Oscar Mateo (2017-09-28 23:40:39)
> > 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>
>
> Tested-by: Chris Wilson <chris@chris-wilson.co.uk> #bxt
>
> Now we just need Mika for the full set of tags! :)
Mika, ping?
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-10-03 12:52 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
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 [this message]
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=1507035118.4728.58.camel@linux.intel.com \
--to=joonas.lahtinen@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox