From: Eric Anholt Subject: Re: [PATCH] drm/i915/vlv: Added write-enable pte bit support Date: Sat, 08 Feb 2014 12:13:48 -0800 Message-ID: <87d2ixjrb7.fsf@eliezer.anholt.net> References: <1389270274-13826-1-git-send-email-akash.goel@intel.com> <87lhxnudfi.fsf@eliezer.anholt.net> <8BF5CF93467D8C498F250C96583BC09CC6CD8D@BGSMSX103.gar.corp.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0074506652==" Return-path: In-Reply-To: <8BF5CF93467D8C498F250C96583BC09CC6CD8D@BGSMSX103.gar.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: "Goel, Akash" , "intel-gfx@lists.freedesktop.org" Cc: "Sharma, Ankitprasad R" List-Id: intel-gfx@lists.freedesktop.org --===============0074506652== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable "Goel, Akash" writes: >>> What happens when we GTT-mapped write a batchbuffer that had > previously been silently made RO by the kernel? Does the CPU take a > fault? We tested this particular case, doing the relocation inside > the Batch buffer, which is mapped to GTT as read-only, from the > exec-buffer path. On doing so, there were no faults observed on the > CPU side. >=20=20 > Also we don't see any ring hangs, when forcing the GPU to do a write > access on the buffers marked as RO. Just the writes were getting > rejected. Interesting. Good to know. So far we've never done self-modifying batches. If we could do it, we had some interesting ideas for handling some classes of state updates, but I think at least at one point the kernel was banning self-modifying batches. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJS9o/8AAoJELXWKTbR/J7oSgAP/35R723KdHASDLXc1I80sQN/ kGB1q7dfBGS/ls09efVvxe/2M1Tt6V+49oFgsp+bC3yT6GIFEoBv4Kx07aMUXwpn 0sKhJIwsfNUF3yzNGpY50V6io41PLOqy0yNsZ4G+7MJsCltirq2urX1/keUV4Ufl 5js+cXKE480Hy3v/8UL1ZPXYzZn82PKyS+Pxb4OuUgcSeFX1KAbF9wwZqL1WtMj7 lIBbjWZLuzILiLlSqblosPGYf/LiFoi4IWYSYOcCZANKijW79MN7ajlJOsqsDjtI dcchNabkGnWJHqWXtFD3stKZsVe5CfhHr+wpbM8LTmAg1Ut6pqWXXrtTOFzYTXmt Jt5EZa1JnCMDrGpbVzX1dJ5RmtaFplNvsklCls39uj++zlI7mP3AiQQcZTotFr9w 3YJJQxXTnenWSE2Uvvdy8H9S1SH749vYD4jryW4q3zKEwEV87qCLommJGEip9FIK bH97JEBLK3i7QtlB7KVKph64npNnlu/CF8QPsepw3YvLarpD2EBivA7azNlSPJ98 bmLMe9IsS1/LRbXexNCljhDuWjVASkkkU4afTI7WuSEHPKGxiJ6zgjQSOO2ih1dE uS2OPD0HcR6ofiVbLx0/tY+w9COzBzjvNPEKBs222XhxunBG3AP0UQSHv6Ds+u5b ofLRuvCcWubYSAtV8POJ =e4+x -----END PGP SIGNATURE----- --=-=-=-- --===============0074506652== 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 --===============0074506652==--