All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cheah, Douglas" <douglas.cheah@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Valleyview: 3DSTATE_URB_VS Minimum URB Entries
Date: Tue, 3 Jul 2012 04:07:35 +0000	[thread overview]
Message-ID: <56F47131CD0B6E46806703F9356EF8D722105FEE@PGSMSX101.gar.corp.intel.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]

Hello folks,

I am seeing corruption when running spectex from mesa demos which looks like vertex being randomly clipped on Valleyview, however spectex works fine on Ivy Bridge.

After tracing down the codes I realize that the current Mesa driver would program the maximum number or URB entries (512 Valleyview)  whenever possible. This conflict with the 3D pipeline PRM where it states there is a programming restriction if the URB Entry Allocation Size is less than 9 URB entries then total entries should be program to 32. After modifying the codes to meet the restriction I was able to run spectex without corruption on Valleyview, pretty surprise that Ivy Bridge did not have this problem.

Here is the code snippet that I have changed which is at this point a quick hack and not upstream worthy as you can see the macro is not even properly defined in brw_defeines.h. Appreciate if I could get opinions from folks who are more familiar with Mesa and more experience with the graphic core.


static void
gen7_upload_urb(struct brw_context *brw)
{
   struct intel_context *intel = &brw->intel;
   /* Total space for entries is URB size - 16kB for push constants */
   int handle_region_size = (brw->urb.size - 16) * 1024; /* bytes */

   /* CACHE_NEW_VS_PROG */
   brw->urb.vs_size = MAX2(brw->vs.prog_data->urb_entry_size, 1);

   int nr_vs_entries = handle_region_size / (brw->urb.vs_size * 64);
   if (nr_vs_entries > brw->urb.max_vs_entries)
      nr_vs_entries = brw->urb.max_vs_entries;

   /* If the number of URB Allocation Size is smaller than 9 512 bit
    * units set the number or URB to Entries to 32
    */
#define GEN7_URB_VS_MIN_ENTRIES 32
   if(brw->urb.vs_size < 9)
        nr_vs_entries = GEN7_URB_VS_MIN_ENTRIES;



Douglas

[-- Attachment #1.2: Type: text/html, Size: 7854 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2012-07-03  4:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  4:07 Cheah, Douglas [this message]
2012-07-03 19:27 ` Valleyview: 3DSTATE_URB_VS Minimum URB Entries Jesse Barnes
2012-07-04  5:50   ` Cheah, Douglas

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=56F47131CD0B6E46806703F9356EF8D722105FEE@PGSMSX101.gar.corp.intel.com \
    --to=douglas.cheah@intel.com \
    --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.