akash.goel@xxxxxxxxx writes: > From: Akash Goel <akash.goel@xxxxxxxxx> > > This adds support for using the write-enable bit in the GTT entry for VLV. > This is handled via a read-only flag in the GEM buffer object which > is then used to check if the write-enable bit has to be set or not > when writing the GTT entries. > Currently by default only the Batch buffer & Ring buffers are being marked > as read only. 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?
Attachment:
pgprbti9FwrPx.pgp
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
