[PATCH 1/3] drm/amdgpu: Add flag for allocating memory for sensitive data

[Michel Dänzer]

On 2019-07-09 7:32 a.m., Kuehling, Felix wrote:
> This memory allocation flag will be used to indicate BOs containing
> sensitive data that should not be leaked to other processes.
> 
> Signed-off-by: Felix Kuehling <Felix.Kuehling at amd.com>
> ---
>  include/uapi/drm/amdgpu_drm.h | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/include/uapi/drm/amdgpu_drm.h b/include/uapi/drm/amdgpu_drm.h
> index 61870478bc9c..58659c28c26e 100644
> --- a/include/uapi/drm/amdgpu_drm.h
> +++ b/include/uapi/drm/amdgpu_drm.h
> @@ -131,6 +131,10 @@ extern "C" {
>   * for the second page onward should be set to NC.
>   */
>  #define AMDGPU_GEM_CREATE_MQD_GFX9		(1 << 8)
> +/* Flag that BO may contain sensitive data that must be cleared before
> + * releasing the memory
> + */
> +#define AMDGPU_GEM_CREATE_VRAM_SENSITIVE	(1 << 9)
>  
>  struct drm_amdgpu_gem_create_in  {
>  	/** the requested memory size */
> 

This flag essentially means "Please don't leak my BO contents".
Similarly, AMDGPU_GEM_CREATE_VRAM_CLEARED essentially means "Please
don't let me see previous memory contents".

I'd argue that neither flag should really be needed; BO contents
shouldn't be leaked by default.


-- 
Earthling Michel Dänzer               |              https://www.amd.com
Libre software enthusiast             |             Mesa and X developer