From: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] rendercopy/bdw: Enable hw-generated binding tables
Date: Wed, 07 May 2014 23:59:23 +0300 [thread overview]
Message-ID: <3751304.js4FzVGZxl@abj-desktop> (raw)
In-Reply-To: <20140507114931.GG18465@intel.com>
On Wednesday, May 07, 2014 02:49:31 PM Ville Syrjälä wrote:
> I quickly cobbled together a hsw version of this and gave it a whirl on
> one machine. Seems to work just fine here, and no lockups when switching
> between hw and sw binding tables. Did you get the lockups on hsw even
> with rendercopy?
>
> Here's my hsw version:
>
>
> +static void
> +gen7_hw_binding_table(struct intel_batchbuffer *batch, bool enable)
> +{
> + if (!enable) {
> + OUT_BATCH(MI_RS_CONTROL | 0x0);
> +
> + OUT_BATCH(HSW_3DSTATE_BINDING_TABLE_POOL_ALLOC | (3 - 2));
> + /* binding table pool base address */
This bit I missed and the source of my troubles for the past few months.
> + OUT_BATCH(3 << 5);
Yep, I confirm toggling on HSW does work quite well now. I'll now update the
patches to include HSW path on the kernel. I also take back my previous
statement that RS is broken on HSW! :)
Thanks a lot Ville!
> + /* Upper bound */
> + OUT_BATCH(0);
> +
> + OUT_BATCH(GEN7_PIPE_CONTROL | (4 - 2));
> + OUT_BATCH(GEN7_PIPE_CONTROL_CS_STALL |
> GEN7_PIPE_CONTROL_STALL_AT_SCOREBOARD); + OUT_BATCH(0);
> + OUT_BATCH(0);
> +
> + OUT_BATCH(GEN7_PIPE_CONTROL | (4 - 2));
> + OUT_BATCH(GEN7_PIPE_CONTROL_SC_INVALIDATE);
> + OUT_BATCH(0);
> + OUT_BATCH(0);
> +
> + return;
> + }
next prev parent reply other threads:[~2014-05-07 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 19:48 igt tests/rendercopy: Add option to test resource streamer functionality Abdiel Janulgue
2014-05-06 19:48 ` [PATCH 1/2] rendercopy/bdw: Enable hw-generated binding tables Abdiel Janulgue
2014-05-06 21:38 ` Ville Syrjälä
2014-05-06 22:09 ` Abdiel Janulgue
2014-05-07 11:49 ` Ville Syrjälä
2014-05-07 11:55 ` Chris Wilson
2014-05-07 20:59 ` Abdiel Janulgue [this message]
2014-05-08 9:54 ` Ville Syrjälä
2014-05-08 10:18 ` Ville Syrjälä
2014-05-12 16:40 ` Daniel Vetter
2014-05-16 11:36 ` Chris Wilson
2014-05-16 14:27 ` Daniel Vetter
2014-05-16 14:45 ` Chris Wilson
2014-05-16 15:07 ` Daniel Vetter
2014-05-06 19:48 ` [PATCH 2/2] tests/gem_render_copy: Add option to test resource streamer Abdiel Janulgue
2014-05-06 20:19 ` igt tests/rendercopy: Add option to test resource streamer functionality Daniel Vetter
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=3751304.js4FzVGZxl@abj-desktop \
--to=abdiel.janulgue@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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