Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>, intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Maarten Lankhorst <dev@lankhorst.se>
Subject: Re: [PATCH 0/3] drm/xe: Disable stolen memory for driver allocations.
Date: Tue, 28 Jul 2026 12:17:57 +0300	[thread overview]
Message-ID: <e7d8aefbafaaf5284c48d671a6951c8c8a614153@intel.com> (raw)
In-Reply-To: <20260630135523.1775379-1-dev@lankhorst.se>

On Tue, 30 Jun 2026, Maarten Lankhorst <dev@lankhorst.se> wrote:
> Using stolen memory has effect on system stability on integrated at high load,
> and causes increased latency waking up from media C6 state.
>
> Only use stolen memory when needed, which is for GSC firmware and FBC.
>
> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/7513
>
> Maarten Lankhorst (3):
>   drm/xe: Avoid using stolen memory for DPT.
>   drm/xe/display: Avoid using stolen memory for framebuffer when media
>     gt exists.

AFAICT this patch was not merged at all, but patches 1 and 3 were,
i.e. what was merged was never tested. This is not how we're supposed to
roll.

BR,
Jani.

>   drm/xe/display: Do not allocate into stolen for new framebuffers.
>
>  drivers/gpu/drm/xe/display/xe_display_bo.c | 40 +++++++---------------
>  drivers/gpu/drm/xe/display/xe_fb_pin.c     | 33 +++++-------------
>  2 files changed, 21 insertions(+), 52 deletions(-)

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2026-07-28  9:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 13:55 [PATCH 0/3] drm/xe: Disable stolen memory for driver allocations Maarten Lankhorst
2026-06-30 13:55 ` [PATCH 1/3] drm/xe: Avoid using stolen memory for DPT Maarten Lankhorst
2026-06-30 14:10   ` Matthew Auld
2026-07-01 10:14     ` Maarten Lankhorst
2026-07-01 10:20       ` Matthew Auld
2026-06-30 13:55 ` [PATCH 2/3] drm/xe/display: Avoid using stolen memory for framebuffer when media gt exists Maarten Lankhorst
2026-07-01 10:27   ` Matthew Auld
2026-07-01 10:28     ` Matthew Auld
2026-06-30 13:55 ` [PATCH 3/3] drm/xe/display: Do not allocate into stolen for new framebuffers Maarten Lankhorst
2026-07-01 10:33   ` Matthew Auld
2026-06-30 14:25 ` ✓ CI.KUnit: success for drm/xe: Disable stolen memory for driver allocations Patchwork
2026-06-30 14:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-01  6:40 ` ✓ Xe.CI.FULL: " Patchwork
2026-07-28  9:17 ` Jani Nikula [this message]

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=e7d8aefbafaaf5284c48d671a6951c8c8a614153@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dev@lankhorst.se \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.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