From: Matthew Auld <matthew.auld@intel.com>
To: Ilia Levi <ilia.levi@intel.com>, intel-xe@lists.freedesktop.org
Cc: koby.elbaz@intel.com, meny.yossefi@intel.com,
shuicheng.lin@intel.com, thomas.hellstrom@intel.com,
matthew.brost@intel.com
Subject: Re: [PATCH v3 1/7] drm/xe/mmio_gem: forbid VMA split
Date: Thu, 23 Jul 2026 17:25:06 +0100 [thread overview]
Message-ID: <b6640f65-df11-431a-a8a5-61fd65c407c9@intel.com> (raw)
In-Reply-To: <20260723161832.137153-2-ilia.levi@intel.com>
On 23/07/2026 17:18, Ilia Levi wrote:
> The fault handler assumes it always operates on a VMA spanning the entire
> GEM object. This does not hold when the VMA has been split, e.g. by a
> partial munmap or mprotect. In that case the handler may map wrong
> physical pages or cause SIGBUS.
>
> Handle this by forbidding VMA split, as partial unmaps are not deemed
> useful for MMIO GEMs.
>
> Suggested-by: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Ilia Levi <ilia.levi@intel.com>
> Fixes: 1ffcf8b8ae8a ("drm/xe: Support for mmap-ing mmio regions")
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/xe/xe_mmio_gem.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_mmio_gem.c b/drivers/gpu/drm/xe/xe_mmio_gem.c
> index 8c803ef233cc..f15a6a84af15 100644
> --- a/drivers/gpu/drm/xe/xe_mmio_gem.c
> +++ b/drivers/gpu/drm/xe/xe_mmio_gem.c
> @@ -39,10 +39,20 @@ struct xe_mmio_gem {
> phys_addr_t phys_addr;
> };
>
> +static int xe_mmio_gem_vm_may_split(struct vm_area_struct *area, unsigned long addr)
> +{
> + /*
> + * Forbid splitting. Together with VM_DONTEXPAND, this keeps the VMA
> + * matching the GEM object exactly.
> + */
> + return -EINVAL;
> +}
> +
> static const struct vm_operations_struct vm_ops = {
> .open = drm_gem_vm_open,
> .close = drm_gem_vm_close,
> .fault = xe_mmio_gem_vm_fault,
> + .may_split = xe_mmio_gem_vm_may_split,
> };
>
> static const struct drm_gem_object_funcs xe_mmio_gem_funcs = {
next prev parent reply other threads:[~2026-07-23 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 16:18 [PATCH v3 0/7] drm/xe/mmio_gem: fix fault handler and destroy path Ilia Levi
2026-07-23 16:18 ` [PATCH v3 1/7] drm/xe/mmio_gem: forbid VMA split Ilia Levi
2026-07-23 16:25 ` Matthew Auld [this message]
2026-07-23 16:18 ` [PATCH v3 2/7] drm/xe/mmio_gem: use write-back mapping for dummy page Ilia Levi
2026-07-23 17:16 ` Matthew Auld
2026-07-24 9:49 ` Levi, Ilia
2026-07-28 16:37 ` Matthew Auld
2026-07-23 16:18 ` [PATCH v3 3/7] drm/xe/mmio_gem: simplify fault handler loop Ilia Levi
2026-07-23 17:22 ` Matthew Auld
2026-07-23 16:18 ` [PATCH v3 4/7] drm/xe/mmio_gem: Revoke drm_vma_node on xe_mmio_gem destroy Ilia Levi
2026-07-23 16:18 ` [PATCH v3 5/7] drm/xe/mmio_gem: cache the dummy page per object Ilia Levi
2026-07-28 16:33 ` Matthew Auld
2026-07-23 16:18 ` [PATCH v3 6/7] drm/xe/mmio_gem: fix destroy flow Ilia Levi
2026-07-24 12:50 ` Matthew Auld
2026-07-23 16:18 ` [PATCH v3 7/7] drm/xe: convert PCI barrier mmap to use xe_mmio_gem Ilia Levi
2026-07-23 16:59 ` ✓ CI.KUnit: success for drm/xe/mmio_gem: fix fault handler and destroy path (rev3) Patchwork
2026-07-23 17:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-24 17:14 ` ✓ Xe.CI.FULL: " Patchwork
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=b6640f65-df11-431a-a8a5-61fd65c407c9@intel.com \
--to=matthew.auld@intel.com \
--cc=ilia.levi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=koby.elbaz@intel.com \
--cc=matthew.brost@intel.com \
--cc=meny.yossefi@intel.com \
--cc=shuicheng.lin@intel.com \
--cc=thomas.hellstrom@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.