All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>,
	"Syrjala, Ville" <ville.syrjala@linux.intel.com>
Cc: "Dave Airlie" <airlied@linux.ie>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Wilson, Chris" <chris@chris-wilson.co.uk>,
	"Melissa Wen" <melissa.srw@gmail.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/vgem: Implement mmap as GEM object function
Date: Fri, 9 Jul 2021 13:51:41 +0200	[thread overview]
Message-ID: <c1131f8b-950e-6f2d-4e6c-60e7c2fa4fb7@suse.de> (raw)
In-Reply-To: <CAKMK7uEe_JaT7kBopoZtgNW_3rDgn-nr2fbycmVuGQAUsb34tA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4572 bytes --]

Hi

Am 08.07.21 um 23:37 schrieb Daniel Vetter:
> On Thu, Jun 24, 2021 at 11:52 AM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>>
>> Moving the driver-specific mmap code into a GEM object function allows
>> for using DRM helpers for various mmap callbacks.
>>
>> The respective vgem functions are being removed. The file_operations
>> structure vgem_driver_fops is now being created by the helper macro
>> DEFINE_DRM_GEM_FOPS().
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> 
> Might be this one, might be a different one (there's also a bunch of
> core kernel patches that got into drm-tip together with this patch),
> but vgem goes boom after this landed in CI:
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/igt@vgem_basic@unload.html
> 
> Can you pls take a quick look? It's in dma-buf fault stuff, so not
> entirely unlikely. Ville pointed this out on irc.

The patch at

 
https://lore.kernel.org/dri-devel/20210709114731.31467-1-tzimmermann@suse.de/T/#u

fixes the issue for me.

Best regards
Thomas

> -Daniel
> 
>> ---
>>   drivers/gpu/drm/vgem/vgem_drv.c | 46 ++++-----------------------------
>>   1 file changed, 5 insertions(+), 41 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
>> index bf38a7e319d1..df634aa52638 100644
>> --- a/drivers/gpu/drm/vgem/vgem_drv.c
>> +++ b/drivers/gpu/drm/vgem/vgem_drv.c
>> @@ -239,32 +239,7 @@ static struct drm_ioctl_desc vgem_ioctls[] = {
>>          DRM_IOCTL_DEF_DRV(VGEM_FENCE_SIGNAL, vgem_fence_signal_ioctl, DRM_RENDER_ALLOW),
>>   };
>>
>> -static int vgem_mmap(struct file *filp, struct vm_area_struct *vma)
>> -{
>> -       unsigned long flags = vma->vm_flags;
>> -       int ret;
>> -
>> -       ret = drm_gem_mmap(filp, vma);
>> -       if (ret)
>> -               return ret;
>> -
>> -       /* Keep the WC mmaping set by drm_gem_mmap() but our pages
>> -        * are ordinary and not special.
>> -        */
>> -       vma->vm_flags = flags | VM_DONTEXPAND | VM_DONTDUMP;
>> -       return 0;
>> -}
>> -
>> -static const struct file_operations vgem_driver_fops = {
>> -       .owner          = THIS_MODULE,
>> -       .open           = drm_open,
>> -       .mmap           = vgem_mmap,
>> -       .poll           = drm_poll,
>> -       .read           = drm_read,
>> -       .unlocked_ioctl = drm_ioctl,
>> -       .compat_ioctl   = drm_compat_ioctl,
>> -       .release        = drm_release,
>> -};
>> +DEFINE_DRM_GEM_FOPS(vgem_driver_fops);
>>
>>   static struct page **vgem_pin_pages(struct drm_vgem_gem_object *bo)
>>   {
>> @@ -387,24 +362,12 @@ static void vgem_prime_vunmap(struct drm_gem_object *obj, struct dma_buf_map *ma
>>          vgem_unpin_pages(bo);
>>   }
>>
>> -static int vgem_prime_mmap(struct drm_gem_object *obj,
>> -                          struct vm_area_struct *vma)
>> +static int vgem_prime_mmap(struct drm_gem_object *obj, struct vm_area_struct *vma)
>>   {
>> -       int ret;
>> -
>> -       if (obj->size < vma->vm_end - vma->vm_start)
>> -               return -EINVAL;
>> -
>> -       if (!obj->filp)
>> -               return -ENODEV;
>> -
>> -       ret = call_mmap(obj->filp, vma);
>> -       if (ret)
>> -               return ret;
>> -
>>          vma_set_file(vma, obj->filp);
>>          vma->vm_flags |= VM_DONTEXPAND | VM_DONTDUMP;
>>          vma->vm_page_prot = pgprot_writecombine(vm_get_page_prot(vma->vm_flags));
>> +       vma->vm_page_prot = pgprot_decrypted(vma->vm_page_prot);
>>
>>          return 0;
>>   }
>> @@ -416,6 +379,7 @@ static const struct drm_gem_object_funcs vgem_gem_object_funcs = {
>>          .get_sg_table = vgem_prime_get_sg_table,
>>          .vmap = vgem_prime_vmap,
>>          .vunmap = vgem_prime_vunmap,
>> +       .mmap = vgem_prime_mmap,
>>          .vm_ops = &vgem_gem_vm_ops,
>>   };
>>
>> @@ -433,7 +397,7 @@ static const struct drm_driver vgem_driver = {
>>          .prime_fd_to_handle = drm_gem_prime_fd_to_handle,
>>          .gem_prime_import = vgem_prime_import,
>>          .gem_prime_import_sg_table = vgem_prime_import_sg_table,
>> -       .gem_prime_mmap = vgem_prime_mmap,
>> +       .gem_prime_mmap = drm_gem_prime_mmap,
>>
>>          .name   = DRIVER_NAME,
>>          .desc   = DRIVER_DESC,
>> --
>> 2.32.0
>>
> 
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2021-07-09 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  9:52 [PATCH] drm/vgem: Implement mmap as GEM object function Thomas Zimmermann
2021-06-24  9:57 ` Christian König
2021-07-08 21:37 ` Daniel Vetter
2021-07-09 11:51   ` Thomas Zimmermann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c1131f8b-950e-6f2d-4e6c-60e7c2fa4fb7@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@ziepe.ca \
    --cc=lee.jones@linaro.org \
    --cc=melissa.srw@gmail.com \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.