All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cheah, Douglas" <douglas.cheah@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: Valleyview: 3DSTATE_URB_VS Minimum URB Entries
Date: Wed, 4 Jul 2012 05:50:24 +0000	[thread overview]
Message-ID: <56F47131CD0B6E46806703F9356EF8D7221079C8@PGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <95f2bebc-0363-4dbd-9ea1-5a143209a6a1@email.android.com>

Will do, I am not familiar with the procedure in Mesa but I will post a patch in their mailing list requesting for it to be included.
I just had a chance to test this on a couple more mesa demo applications and 3DMarkmobile that also exhibit a lot of corruptions in Valleyview. The fix work well for those application as well.

Douglas

-----Original Message-----
From: Jesse Barnes [mailto:jbarnes@virtuousgeek.org] 
Sent: Wednesday, July 04, 2012 3:28 AM
To: Cheah, Douglas; intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Valleyview: 3DSTATE_URB_VS Minimum URB Entries

"Cheah, Douglas" <douglas.cheah@intel.com> wrote:

>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
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/intel-gfx

ooh this is a good fix. Can you bounce it over to the meas list for inclusion? 
--
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2012-07-04  5:50 UTC|newest]

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

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=56F47131CD0B6E46806703F9356EF8D7221079C8@PGSMSX101.gar.corp.intel.com \
    --to=douglas.cheah@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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.