mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"Huang, Ray" <Ray.Huang@amd.com>, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel@ffwll.ch>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 06/11] drm/ttm: factor out ttm_bo_mmap_vma_setup
Date: Thu, 17 Oct 2019 11:06:33 +0000	[thread overview]
Message-ID: <398f5818-296d-67cc-2447-d3075187bf0c@amd.com> (raw)
In-Reply-To: <c08921f8-8ae9-55aa-c472-6b660b96576b@amd.com>

Am 16.10.19 um 14:18 schrieb Christian König:
> Am 16.10.19 um 13:51 schrieb Gerd Hoffmann:
>> Factor out ttm vma setup to a new function.
>> Reduces code duplication a bit.
>>
>> v2: don't change vm_flags (moved to separate patch).
>> v4: make ttm_bo_mmap_vma_setup static.
>>
>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com> for this one 
> and #7 in the series.

Any objections that I add these two to my drm-ttm-next pull request or 
did you wanted to merge that through some other tree?

Thanks,
Christian.

>
>> ---
>>   drivers/gpu/drm/ttm/ttm_bo_vm.c | 46 +++++++++++++++++----------------
>>   1 file changed, 24 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_bo_vm.c 
>> b/drivers/gpu/drm/ttm/ttm_bo_vm.c
>> index 4aa007edffb0..53345c0854d5 100644
>> --- a/drivers/gpu/drm/ttm/ttm_bo_vm.c
>> +++ b/drivers/gpu/drm/ttm/ttm_bo_vm.c
>> @@ -426,6 +426,28 @@ static struct ttm_buffer_object 
>> *ttm_bo_vm_lookup(struct ttm_bo_device *bdev,
>>       return bo;
>>   }
>>   +static void ttm_bo_mmap_vma_setup(struct ttm_buffer_object *bo, 
>> struct vm_area_struct *vma)
>> +{
>> +    vma->vm_ops = &ttm_bo_vm_ops;
>> +
>> +    /*
>> +     * Note: We're transferring the bo reference to
>> +     * vma->vm_private_data here.
>> +     */
>> +
>> +    vma->vm_private_data = bo;
>> +
>> +    /*
>> +     * We'd like to use VM_PFNMAP on shared mappings, where
>> +     * (vma->vm_flags & VM_SHARED) != 0, for performance reasons,
>> +     * but for some reason VM_PFNMAP + x86 PAT + write-combine is very
>> +     * bad for performance. Until that has been sorted out, use
>> +     * VM_MIXEDMAP on all mappings. See freedesktop.org bug #75719
>> +     */
>> +    vma->vm_flags |= VM_MIXEDMAP;
>> +    vma->vm_flags |= VM_IO | VM_DONTEXPAND | VM_DONTDUMP;
>> +}
>> +
>>   int ttm_bo_mmap(struct file *filp, struct vm_area_struct *vma,
>>           struct ttm_bo_device *bdev)
>>   {
>> @@ -449,24 +471,7 @@ int ttm_bo_mmap(struct file *filp, struct 
>> vm_area_struct *vma,
>>       if (unlikely(ret != 0))
>>           goto out_unref;
>>   -    vma->vm_ops = &ttm_bo_vm_ops;
>> -
>> -    /*
>> -     * Note: We're transferring the bo reference to
>> -     * vma->vm_private_data here.
>> -     */
>> -
>> -    vma->vm_private_data = bo;
>> -
>> -    /*
>> -     * We'd like to use VM_PFNMAP on shared mappings, where
>> -     * (vma->vm_flags & VM_SHARED) != 0, for performance reasons,
>> -     * but for some reason VM_PFNMAP + x86 PAT + write-combine is very
>> -     * bad for performance. Until that has been sorted out, use
>> -     * VM_MIXEDMAP on all mappings. See freedesktop.org bug #75719
>> -     */
>> -    vma->vm_flags |= VM_MIXEDMAP;
>> -    vma->vm_flags |= VM_IO | VM_DONTEXPAND | VM_DONTDUMP;
>> +    ttm_bo_mmap_vma_setup(bo, vma);
>>       return 0;
>>   out_unref:
>>       ttm_bo_put(bo);
>> @@ -481,10 +486,7 @@ int ttm_fbdev_mmap(struct vm_area_struct *vma, 
>> struct ttm_buffer_object *bo)
>>         ttm_bo_get(bo);
>>   -    vma->vm_ops = &ttm_bo_vm_ops;
>> -    vma->vm_private_data = bo;
>> -    vma->vm_flags |= VM_MIXEDMAP;
>> -    vma->vm_flags |= VM_IO | VM_DONTEXPAND;
>> +    ttm_bo_mmap_vma_setup(bo, vma);
>>       return 0;
>>   }
>>   EXPORT_SYMBOL(ttm_fbdev_mmap);
>


  reply	other threads:[~2019-10-17 11:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191016115203.20095-1-kraxel@redhat.com>
2019-10-16 11:51 ` [PATCH v4 01/11] drm: add mmap() to drm_gem_object_funcs Gerd Hoffmann
2019-10-16 11:51 ` [PATCH v4 02/11] drm/shmem: switch shmem helper to &drm_gem_object_funcs.mmap Gerd Hoffmann
2019-10-16 11:51 ` [PATCH v4 03/11] drm/shmem: drop VM_DONTDUMP Gerd Hoffmann
2019-10-16 11:51 ` [PATCH v4 04/11] drm/shmem: drop VM_IO Gerd Hoffmann
2019-10-16 11:51 ` [PATCH v4 05/11] drm/shmem: drop DEFINE_DRM_GEM_SHMEM_FOPS Gerd Hoffmann
2019-10-16 11:51 ` [PATCH v4 06/11] drm/ttm: factor out ttm_bo_mmap_vma_setup Gerd Hoffmann
2019-10-16 12:18   ` Koenig, Christian
2019-10-17 11:06     ` Koenig, Christian [this message]
2019-10-17 12:30       ` Gerd Hoffmann
2019-10-17 16:48         ` Koenig, Christian
2019-10-16 11:51 ` [PATCH v4 07/11] drm/ttm: rename ttm_fbdev_mmap Gerd Hoffmann
2019-10-16 11:52 ` [PATCH v4 08/11] drm/ttm: add drm_gem_ttm_mmap() Gerd Hoffmann
2019-10-16 15:04   ` Daniel Vetter
2019-10-16 11:52 ` [PATCH v4 09/11] drm/vram: switch vram helper to &drm_gem_object_funcs.mmap() Gerd Hoffmann
2019-10-16 11:52 ` [PATCH v4 10/11] drm/vram: drop verify_access Gerd Hoffmann
2019-10-16 11:52 ` [PATCH v4 11/11] drm/vram: drop DRM_VRAM_MM_FILE_OPERATIONS Gerd Hoffmann

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=398f5818-296d-67cc-2447-d3075187bf0c@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome