dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Torrente <igor.torrente@collabora.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: loic.molinari@collabora.com, willy@infradead.org,
	frank.binns@imgtec.com,  matt.coster@imgtec.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, simona@ffwll.ch,
	dri-devel@lists.freedesktop.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 5/6] drm/gem-shmem: Track folio accessed/dirty status in mmap
Date: Wed, 27 May 2026 12:02:48 -0300	[thread overview]
Message-ID: <16cbd262-aa82-4ca7-ac12-d587ed78ff3b@collabora.com> (raw)
In-Reply-To: <025ee28d-c941-4cf1-a6cf-565686ea0bec@suse.de>

Hi Tomas,

I tested your patch and Boris's modifications on top of your patch, and
I'm happy to report that both seem to work just fine.

BR,
Igor Torrente

On 5/27/26 07:32, Thomas Zimmermann wrote:
> Hi
>
> Am 27.05.26 um 12:18 schrieb Boris Brezillon:
>> Hello Thomas,
>>
>> I'm inlining the diff you posted so I can comment on it directly before
>> it's officially posted to the list.
>
> Thanks, I'll incorporate those in the next test rev or the official 
> patch.
>
> Best regards
> Thomas
>
>>
>> On Wed, 27 May 2026 08:56:33 +0200
>> Thomas Zimmermann <tzimmermann@suse.de> wrote:
>>
>>> diff --git a/drivers/gpu/drm/drm_gem_shmem_helper.c 
>>> b/drivers/gpu/drm/drm_gem_shmem_helper.c
>>> index 545933c7f712..07e117673124 100644
>>> --- a/drivers/gpu/drm/drm_gem_shmem_helper.c
>>> +++ b/drivers/gpu/drm/drm_gem_shmem_helper.c
>>> @@ -554,21 +554,6 @@ int drm_gem_shmem_dumb_create(struct drm_file 
>>> *file, struct drm_device *dev,
>>>   }
>>>   EXPORT_SYMBOL_GPL(drm_gem_shmem_dumb_create);
>>>   -static void drm_gem_shmem_record_mkwrite(struct vm_fault *vmf)
>>> -{
>>> -    struct vm_area_struct *vma = vmf->vma;
>>> -    struct drm_gem_object *obj = vma->vm_private_data;
>>> -    struct drm_gem_shmem_object *shmem = to_drm_gem_shmem_obj(obj);
>>> -    loff_t num_pages = obj->size >> PAGE_SHIFT;
>>> -    pgoff_t page_offset = vmf->pgoff - vma->vm_pgoff; /* page 
>>> offset within VMA */
>>> -
>>> -    if (drm_WARN_ON(obj->dev, !shmem->pages || page_offset >= 
>>> num_pages))
>>> -        return;
>>> -
>>> -    file_update_time(vma->vm_file);
>>> - folio_mark_dirty(page_folio(shmem->pages[page_offset]));
>>> -}
>>> -
>>>   static vm_fault_t try_insert_pfn(struct vm_fault *vmf, unsigned 
>>> int order,
>>>                    unsigned long pfn)
>>>   {
>>> @@ -581,23 +566,16 @@ static vm_fault_t try_insert_pfn(struct 
>>> vm_fault *vmf, unsigned int order,
>>>             if (aligned &&
>>> folio_test_pmd_mappable(page_folio(pfn_to_page(pfn)))) {
>>> -            vm_fault_t ret;
>>> -
>>>               pfn &= PMD_MASK >> PAGE_SHIFT;
>>>   -            /* Unlike PTEs which are automatically upgraded to
>>> +            /*
>>> +             * Unlike PTEs which are automatically upgraded to
>>>                * writeable entries, the PMD upgrades go through
>>>                * .huge_fault(). Make sure we pass the "write" info
>>>                * along in that case.
>>> -             * This also means we have to record the write fault
>>> -             * here, instead of in .pfn_mkwrite().
>>>                */
>>> -            ret = vmf_insert_pfn_pmd(vmf, pfn,
>>> -                         vmf->flags & FAULT_FLAG_WRITE);
>>> -            if (ret == VM_FAULT_NOPAGE && (vmf->flags & 
>>> FAULT_FLAG_WRITE))
>>> -                drm_gem_shmem_record_mkwrite(vmf);
>>> -
>>> -            return ret;
>>> +            return vmf_insert_pfn_pmd(vmf, pfn,
>>> +                          vmf->flags & FAULT_FLAG_WRITE);
>> I believe we can go back to
>>
>>             return vmf_insert_pfn_pmd(vmf, pfn, false);
>>
>> if the mappings are no longer adjusted to catch write accesses.
>>
>>>           }
>>>   #endif
>>>       }
>>> @@ -635,8 +613,15 @@ static vm_fault_t 
>>> drm_gem_shmem_any_fault(struct vm_fault *vmf, unsigned int ord
>>>       pfn = page_to_pfn(page);
>>>         ret = try_insert_pfn(vmf, order, pfn);
>>> -    if (ret == VM_FAULT_NOPAGE)
>>> +    if (ret == VM_FAULT_NOPAGE) {
>>>           folio_mark_accessed(folio);
>>> +        /*
>>> +         * Always record write access to the buffer. The natural
>>> +         * place would be pfn_mkwrite, but this breaks KVM.
>>> +         */
>>> +        file_update_time(vma->vm_file);
>>> +        folio_mark_dirty(folio);
>> We can be a bit smarter here:
>>
>>         /*
>>          * Always record write access to the buffer if the
>>          * mapping is writeable. The natural place would be
>>          * pfn_mkwrite, but this breaks KVM.
>>          */
>>         if (vma->vm_flags & VM_WRITE) {
>>             file_update_time(vma->vm_file);
>>             folio_mark_dirty(folio);
>>         }
>>
>>> +    }
>> The rest looks good to me.
>>
>> Regards,
>>
>> Boris
>

  reply	other threads:[~2026-05-27 15:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 13:27 [PATCH v3 0/6] drm/gem-shmem: Track page accessed/dirty status Thomas Zimmermann
2026-02-09 13:27 ` [PATCH v3 1/6] drm/gem-shmem: Use obj directly where appropriate in fault handler Thomas Zimmermann
2026-02-09 14:10   ` Boris Brezillon
2026-02-09 13:27 ` [PATCH v3 2/6] drm/gem-shmem: Test for existence of page in mmap " Thomas Zimmermann
2026-02-09 14:10   ` Boris Brezillon
2026-02-09 13:27 ` [PATCH v3 3/6] drm/gem-shmem: Return vm_fault_t from drm_gem_shmem_try_map_pmd() Thomas Zimmermann
2026-02-09 13:27 ` [PATCH v3 4/6] drm/gem-shmem: Refactor drm_gem_shmem_try_map_pmd() Thomas Zimmermann
2026-02-09 14:25   ` Boris Brezillon
2026-02-09 13:27 ` [PATCH v3 5/6] drm/gem-shmem: Track folio accessed/dirty status in mmap Thomas Zimmermann
2026-02-09 14:23   ` Boris Brezillon
2026-02-09 14:46     ` Thomas Zimmermann
2026-02-09 15:01       ` Boris Brezillon
2026-02-25 11:35         ` Thomas Zimmermann
2026-05-20 13:11   ` Igor Torrente
2026-05-20 14:44     ` Boris Brezillon
2026-05-22  8:31       ` Thomas Zimmermann
2026-05-26 14:44     ` Thomas Zimmermann
2026-05-26 14:56       ` Igor Torrente
2026-05-27  6:56         ` Thomas Zimmermann
2026-05-27 10:18           ` Boris Brezillon
2026-05-27 10:32             ` Thomas Zimmermann
2026-05-27 15:02               ` Igor Torrente [this message]
2026-05-27 15:19                 ` Thomas Zimmermann
2026-05-28  7:20             ` Thomas Zimmermann
2026-05-28  9:11               ` Boris Brezillon
2026-05-28  9:22                 ` Thomas Zimmermann
2026-05-28  9:38                   ` Boris Brezillon
2026-02-09 13:27 ` [PATCH v3 6/6] drm/gem-shmem: Track folio accessed/dirty status in vmap Thomas Zimmermann
2026-02-25 10:57   ` Frank Binns
2026-02-25 11:34     ` Thomas Zimmermann

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=16cbd262-aa82-4ca7-ac12-d587ed78ff3b@collabora.com \
    --to=igor.torrente@collabora.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frank.binns@imgtec.com \
    --cc=linux-mm@kvack.org \
    --cc=loic.molinari@collabora.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt.coster@imgtec.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=willy@infradead.org \
    /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