From: Boris Brezillon <boris.brezillon@collabora.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Pedro Demarchi Gomes <pedrodemargomes@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/shmem-helper: Fix Map huge page mapping in fault handler
Date: Mon, 16 Mar 2026 11:36:37 +0100 [thread overview]
Message-ID: <20260316113637.63a5031a@fedora> (raw)
In-Reply-To: <08112162-7939-48b8-be57-790a8686bc46@suse.de>
On Mon, 16 Mar 2026 11:14:40 +0100
Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Am 16.03.26 um 10:50 schrieb Boris Brezillon:
>
> >> Avoid this race by adding a huge_fault callback to drm_gem_shmem_vm_ops so that
> >> PMD-sized mappings are handled through the appropriate huge page fault path.
>
> This patch will conflict heavily with the folio-tracking patches that
> has been merged into upstream DRM. How do we deal with that?
We need a fix in drm-misc-fixes since it's a bug that exists in v7.0,
and a conflict resolution recorded in drm-tip to deal with the
drm-misc-fixes vs drm-misc-next conflicts (I don't remember the exact
process, but it's documented in dim).
next prev parent reply other threads:[~2026-03-16 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 0:26 [PATCH v3] drm/shmem-helper: Fix Map huge page mapping in fault handler Pedro Demarchi Gomes
2026-03-16 9:14 ` Thomas Zimmermann
2026-03-16 9:28 ` Boris Brezillon
2026-03-16 10:12 ` Thomas Zimmermann
2026-03-16 10:42 ` Boris Brezillon
2026-03-16 9:50 ` Boris Brezillon
2026-03-16 10:14 ` Thomas Zimmermann
2026-03-16 10:36 ` Boris Brezillon [this message]
2026-03-16 12:10 ` Thomas Zimmermann
2026-03-16 13:20 ` Boris Brezillon
2026-03-16 10:03 ` Boris Brezillon
2026-03-16 14:21 ` Boris Brezillon
2026-03-17 17:30 ` Boris Brezillon
2026-03-18 10:16 ` Boris Brezillon
2026-03-18 11:14 ` Pedro Demarchi Gomes
2026-03-18 11:45 ` Boris Brezillon
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=20260316113637.63a5031a@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pedrodemargomes@gmail.com \
--cc=simona@ffwll.ch \
--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 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.