[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f1bd2517-f49f-34c0-6b75-3181c4698f60@arm.com>
Date: Mon, 23 Sep 2019 14:32:32 +0100
From: Steven Price <steven.price@....com>
To: Gerd Hoffmann <kraxel@...hat.com>, dri-devel@...ts.freedesktop.org
Cc: Maxime Ripard <maxime.ripard@...tlin.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
open list <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...ux.ie>,
Thomas Zimmermann <tzimmermann@...e.de>,
Sean Paul <sean@...rly.run>
Subject: Re: [PATCH v2 03/11] drm/shmem: drop VM_DONTDUMP
On 17/09/2019 10:23, Gerd Hoffmann wrote:
> Not obvious why this is needed. According to Deniel Vetter this is most
> likely a historic artefact dating back to the days where drm drivers
> exposed hardware registers as mmap'able gem objects, to avoid dumping
> touching those registers. shmem gem objects surely don't need that ...
>
> Signed-off-by: Gerd Hoffmann <kraxel@...hat.com>
Reviewed-by: Steven Price <steven.price@....com>
> ---
> drivers/gpu/drm/drm_gem_shmem_helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_gem_shmem_helper.c b/drivers/gpu/drm/drm_gem_shmem_helper.c
> index a9a586630517..6efedab15016 100644
> --- a/drivers/gpu/drm/drm_gem_shmem_helper.c
> +++ b/drivers/gpu/drm/drm_gem_shmem_helper.c
> @@ -536,7 +536,7 @@ int drm_gem_shmem_mmap(struct drm_gem_object *obj, struct vm_area_struct *vma)
> return ret;
> }
>
> - vma->vm_flags |= VM_IO | VM_MIXEDMAP | VM_DONTEXPAND | VM_DONTDUMP;
> + vma->vm_flags |= VM_IO | VM_MIXEDMAP | VM_DONTEXPAND;
> vma->vm_page_prot = pgprot_writecombine(vm_get_page_prot(vma->vm_flags));
> vma->vm_page_prot = pgprot_decrypted(vma->vm_page_prot);
> vma->vm_ops = &drm_gem_shmem_vm_ops;
>
Powered by blists - more mailing lists