From: Zhenyu Wang Subject: Re: [PATCH] intel: Add AUB file dump support Date: Wed, 23 Feb 2011 09:49:57 +0800 Message-ID: <20110223014957.GR22867@zhen-devel.sh.intel.com> References: <1297836461-31543-1-git-send-email-zhenyuw@linux.intel.com> <1297836461-31543-2-git-send-email-zhenyuw@linux.intel.com> <1298352046.28271.9.camel@xhh-ctg32> <20110222055132.GN22867@zhen-devel.sh.intel.com> <1298354983.28271.24.camel@xhh-ctg32> <20110222062226.GO22867@zhen-devel.sh.intel.com> <1298357493.28271.33.camel@xhh-ctg32> <20110222065536.GP22867@zhen-devel.sh.intel.com> <87wrksug7x.fsf@pollan.anholt.net> Reply-To: Zhenyu Wang Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1941764864==" Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id BF2589E78C for ; Tue, 22 Feb 2011 17:49:59 -0800 (PST) In-Reply-To: <87wrksug7x.fsf@pollan.anholt.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Eric Anholt Cc: "intel-gfx@lists.freedesktop.org" , "Liu, Yuanhan" List-Id: intel-gfx@lists.freedesktop.org --===============1941764864== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qXPE+6hUsFlDAc0e" Content-Disposition: inline --qXPE+6hUsFlDAc0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011.02.22 09:33:22 -0800, Eric Anholt wrote: > While I originally hacked it up this way where libdrm intuits what kind > of buffer it is from the name of the buffer, it's a bad way to design an > interface. We should really have a command that marks (an area) of a > buffer object as being a particular AUB type, and Mesa would use that > command to mark its buffers as appropriate. Particularly since we're > moving to streaming more of our state buffers into larger buffer > objects. ok, if our plan is to move into larger buffer, current method is just hairy. Like I didn't hack up surface state and some others, coz it's=20 twisted to convert current batch ending space usage into real bo for=20 matching the name for trace block types. >=20 > We also can't commit code to Mesa that just writes into some arbitrary > file based on an environment variable -- keep in mind that our Mesa > driver is loaded from the X Server which is running as root. yeah, I wasn't aware of this, any comment for how to dump the file? --=20 Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827 --qXPE+6hUsFlDAc0e Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1kZ8UACgkQsQQaM014GCeK5QCdEZmxu1FR0pkGeO8XKWUBcy9J uNsAnjd+GQF/5F02JPw7R/aQLBv1Nis8 =sqCU -----END PGP SIGNATURE----- --qXPE+6hUsFlDAc0e-- --===============1941764864== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1941764864==--