From: Gabriel Gama <operatingsystemsdepression@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: patrik.r.jakobsson@gmail.com
Subject: [RFC PATCH 0/6] drm/gma500: prepare GEM and MMU for 3D rendering and hybrid 2D
Date: Mon, 9 Nov 2026 02:54:44 -0300 [thread overview]
Message-ID: <20261109055451.17458-1-operatingsystemsdepression@gmail.com> (raw)
Hi,
These six patches prepare the existing gma500 GEM/MMU code for future
SGX535 3D and hybrid CPU/GPU 2D. They target Linux 7.4-rc2
(7475ea8b58616b33c04afb976cf0fbaad9dd63fb), enable neither acceleration path
and add no rendering ABI or command submission.
Display GTT and SGX page tables keep their existing, separate roles. The
series fixes sizing, unpin underflow and page-table cache-flush lifetime,
makes MMU insertion transactional and propagates setup/pin failures.
Review of the rollback and ownership assumptions would be appreciated.
Offline validation ran in Debian AArch64 userspace under PRoot: i386 LLVM19
W=1 full kernel link with HIGHMEM4G, plus native/UBSan CPU tests. All nine
MMU KUnit cases passed in a separate i386 QEMU TCG guest. Checkpatch reports
zero errors and one MAINTAINERS advisory on the already-covered test file.
Physical Mini12 testing has NOT been performed; display, suspend/removal
and SGX cache visibility remain unqualified. Historical GPU results do
not qualify this series.
Patch list:
1. Use the common dumb-buffer size helper.
2. Prevent GEM unpin underflow.
3. Fix SGX page-table cache-flush mapping lifetime.
4. Make MMU insertion checked and transactional.
5. Propagate MMU setup and GEM pin failures.
6. Add software-only MMU KUnit coverage.
Thanks,
Gabriel Gama
next reply other threads:[~2026-11-09 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 5:54 Gabriel Gama [this message]
2026-11-09 5:54 ` [RFC PATCH 1/6] drm/gma500: use the common dumb-buffer size helper Gabriel Gama
2026-11-09 5:54 ` [RFC PATCH 2/6] drm/gma500: do not underflow an unpinned GEM object Gabriel Gama
2026-11-09 5:54 ` [RFC PATCH 3/6] drm/gma500: Fix SGX page-table cache-flush mapping lifetime Gabriel Gama
2026-11-09 6:00 ` sashiko-bot
2026-11-09 5:54 ` [RFC PATCH 4/6] drm/gma500: Make SGX MMU insertion checked and transactional Gabriel Gama
2026-11-09 5:54 ` [RFC PATCH 5/6] drm/gma500: Propagate SGX MMU setup and GEM pin failures Gabriel Gama
2026-11-09 6:06 ` sashiko-bot
2026-11-09 5:54 ` [RFC PATCH 6/6] drm/gma500: Add software-only KUnit coverage for SGX page tables Gabriel Gama
2026-11-09 6:07 ` sashiko-bot
2026-11-09 6:26 ` Operating System's Depression
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=20261109055451.17458-1-operatingsystemsdepression@gmail.com \
--to=operatingsystemsdepression@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=patrik.r.jakobsson@gmail.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.