On 2018-09-11 9:46 a.m., Christian König wrote: > Am 11.09.2018 um 09:37 schrieb Michel Dänzer: >> On 2018-09-11 8:49 a.m., Christian König wrote: >>> But another question: Why do you want to clear VRAM on allocation? We >>> perfectly support allocating VRAM without clearing it. >> Which is a problem of its own, as it can leak information from one >> process to another. > > How about adding a AMDGPU_GEM_CREATE_VRAM_SECRED flag which triggers > clearing VRAM when the BO is freed?
Doesn't sound like much better API than AMDGPU_GEM_CREATE_VRAM_CLEARED to me. Why would any process be okay with leaking its BO contents to other processes? Could that flag even prevent it in all cases, e.g. when BOs are evicted or otherwise migrated? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
