> Just how many of GPU instructions can be made to sneakily peek/write into host's memory? Ideally, zero. Of course in real life this will be non-zero, but I l

> Just how many of GPU instructions can be made to sneakily peek/write into host's memory? Ideally, zero. Of course in real life this will be non-zero, but I like to believe that with the huge bounty Google offers on chrome vulns, those bugs will be fixed before they could exploit me. (Note that the original page says "Can snoop on cpu host memory via DMA" -- this only works within the process boundary via approved APIs. So basically no extra security risks, this is exactly the same thing that CPU-based LD_PRELOAD files can do already)