From: Junxiao Chang <junxiao.chang@intel.com>
To: jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
matthew.brost@intel.com, thomas.hellstrom@linux.intel.com,
airlied@gmail.com, simona@ffwll.ch, bigeasy@linutronix.de,
clrkwllms@kernel.org, rostedt@goodmis.org,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Cc: dev@lankhorst.se, junxiao.chang@intel.com
Subject: [PATCH 0/2] drm/xe: drm/xe: Improve real-time performance by limiting stolen memory usage
Date: Wed, 4 Nov 2026 11:27:30 +0800 [thread overview]
Message-ID: <20261104032732.30681-1-junxiao.chang@intel.com> (raw)
Stolen memory access and allocation overhead can introduce latency spikes
and jitter, which negatively impacts real-time performance on PREEMPT_RT
kernels.
To improve real-time determinism, this series minimizes stolen memory usage
when running on an RT-enabled kernel:
1. It bypasses initial plane allocation from stolen memory to avoid hardware
access latency, falling back to standard allocations.
2. It warns the user if the GSC microcontroller is active (which relies on
stolen memory) and provides instructions on how to disable it.
Junxiao Chang (2):
drm/xe/display: Skip initial plane allocation from stolen memory on RT
drm/xe/gsc: warn about GSC stolen memory usage on RT kernels
drivers/gpu/drm/xe/display/xe_initial_plane.c | 6 ++++++
drivers/gpu/drm/xe/xe_gsc.c | 5 +++++
2 files changed, 11 insertions(+)
--
2.43.0
next reply other threads:[~2026-11-03 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 3:27 Junxiao Chang [this message]
2026-11-04 3:27 ` [PATCH 1/2] drm/xe/display: Skip initial plane allocation from stolen memory on RT Junxiao Chang
2026-11-03 10:45 ` Maarten Lankhorst
2026-11-04 3:27 ` [PATCH 2/2] drm/xe/gsc: warn about GSC stolen memory usage on RT kernels Junxiao Chang
2026-11-03 11:22 ` Maarten Lankhorst
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=20261104032732.30681-1-junxiao.chang@intel.com \
--to=junxiao.chang@intel.com \
--cc=airlied@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=rostedt@goodmis.org \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®