From: Ben Widawsky <ben@bwidawsk.net>
To: Kenneth Graunke <kenneth@whitecape.org>
Cc: mesa-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Mesa-dev] [PATCH] drm/i915: Enable the HiZ RAW Stall Optimization on Gen8.
Date: Sun, 11 Jan 2015 19:09:38 -0800 [thread overview]
Message-ID: <20150112030937.GA2594@bwidawsk.net> (raw)
In-Reply-To: <2487831.m4DGgTKFrR@vakarian>
On Sun, Jan 11, 2015 at 06:53:32PM -0800, Kenneth Graunke wrote:
[snip]
>
> Jesse had suggested setting it in broadwell_init_clock_gating on January 5th,
> and Valtteri tried it on January 7th. He found "no noticeable difference".
> I tried it again, and confirmed his result: there was zero performance impact.
>
> Setting it via an LRI in Mesa did have a performance impact. I reverted my
> Mesa patch, and tried setting it here, and it had the same performance impact.
> I rebooted between kernels several times to confirm. It works here, but it
> doesn't there.
>
> I'm pretty sure I confirmed the same result with this bit. Feel free to try.
>
That's okay. I believe you, I just thought you may have known something I didn't.
> Perhaps we should move the rest of the per-context bits here instead of
> *_init_clock_gating. We should also confirm that the other bits are actually
> having an effect.
If this is the behavior we're getting, we should absolutely do this.
>
> I don't know why it works on Haswell, but it does there - the HiZ RAW stall
> bit is set via haswell_init_clock_gating, and it's clearly having an impact.
> Maybe it has something to do with the golden context, which is new on BDW.
> But I'm probably wrong about that. Setting it when a context is active does
> seem more reliable...
The golden context stuff has been backported to all gens supported hardware
contexts and/or execlists, so I don't think it's that.
The big difference between the workarounds and init clock gating is the former
is done via LRI, and the latter MMIO. (also, the latter is run again on resume,
and I don't think the former is).
Thinking outloud - what's the default setting for execlists on BDW now? For
execlists my plan (when it was my plan to have) had always been to manually set
the register in the context image before loading it. We don't do that with the
existing code, we use the old ringbuffer style of, hope it preserves the
contents. I wonder if that's the distinction between HSW.
>
> --Ken
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-12 3:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 2:44 [PATCH] drm/i915: Enable the HiZ RAW Stall Optimization on Gen8 Kenneth Graunke
2015-01-11 21:49 ` [Mesa-dev] " Ben Widawsky
2015-01-12 0:05 ` Kenneth Graunke
2015-01-12 1:46 ` Ben Widawsky
2015-01-12 2:53 ` Kenneth Graunke
2015-01-12 3:09 ` Ben Widawsky [this message]
2015-01-12 3:05 ` Kenneth Graunke
2015-01-12 3:14 ` [Mesa-dev] " Ben Widawsky
2015-01-12 12:02 ` Ville Syrjälä
2015-01-12 18:02 ` Ben Widawsky
2015-01-12 18:09 ` Dave Gordon
2015-01-13 2:07 ` Ben Widawsky
2015-01-13 20:03 ` Ville Syrjälä
2015-01-12 12:32 ` [Intel-gfx] " Ville Syrjälä
2015-01-12 21:41 ` Kenneth Graunke
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=20150112030937.GA2594@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.org \
--cc=mesa-dev@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