From: Boris Brezillon <boris.brezillon@collabora.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Igor Torrente <igor.torrente@collabora.com>,
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: Thu, 28 May 2026 11:11:40 +0200 [thread overview]
Message-ID: <20260528111140.2d9535b7@fedora> (raw)
In-Reply-To: <4a00d72c-9b87-4511-9da0-bcb40fae4d74@suse.de>
On Thu, 28 May 2026 09:20:16 +0200
Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Hi
>
> Am 27.05.26 um 12:18 schrieb Boris Brezillon:
> [...]
> >> - 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.
>
> If we don't install it as writable now, won't the kernel not split it up
> into 4KiB pages when the actual write happens?
It will be installed as writeable right away, regardless of the write
parameter, because if pfn_mkwrite is not implemented, vma->vm_page_prot
won't be lowered to read-only in the first place, or at least that's
what I remember from the previous debugging session I've done.
next prev parent reply other threads:[~2026-05-28 9:11 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
2026-05-27 15:19 ` Thomas Zimmermann
2026-05-28 7:20 ` Thomas Zimmermann
2026-05-28 9:11 ` Boris Brezillon [this message]
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=20260528111140.2d9535b7@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=igor.torrente@collabora.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