Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Govindapillai <vinod.govindapillai@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, ville.syrjala@intel.com,
	uma.shankar@intel.com
Subject: [PATCH v2 0/6] update the stolen memory allocation preference
Date: Fri, 20 Feb 2026 19:09:02 +0200	[thread overview]
Message-ID: <20260220170908.201422-1-vinod.govindapillai@intel.com> (raw)

Allocating stolen memory for the fbdev and initial plane bo might
bar enabling FBC. So have some check if we have enough stolen memory
for FBC before allocating the stolen to fbdev and initial plane bo.
Right now the check is based on simple logic that if the fbdev or
initial plane bo take more than half of the stolen, avoid useing the
stolen for that. Later on we will fine tune this by adding some better
comparison based on the possible FBC size.

v2: addressed review comments

Ville Syrjälä (3):
  drm/xe/fbdev: Fix BIOS FB vs.s stolen size check
  drm/i915/fbdev: Extract intel_fbdev_fb_prefer_stolen()
  drm/xe/fbdev: Extract intel_fbdev_fb_prefer_stolen()

Vinod Govindapillai (3):
  drm/i915/display: remove the usage of dev_priv
  drm/xe/fbdev: print info about stolen memory preference for fbdev
  drm/i915/fbdev: print info about stolen memory preference for fbdev

 drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 38 ++++++++++++-------
 drivers/gpu/drm/i915/display/intel_fbdev_fb.h |  1 +
 drivers/gpu/drm/i915/i915_initial_plane.c     |  3 +-
 drivers/gpu/drm/xe/display/intel_fbdev_fb.c   | 27 ++++++++++++-
 drivers/gpu/drm/xe/display/xe_initial_plane.c | 13 ++-----
 5 files changed, 58 insertions(+), 24 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-02-20 17:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 17:09 Vinod Govindapillai [this message]
2026-02-20 17:09 ` [PATCH v2 1/6] drm/xe/fbdev: Fix BIOS FB vs.s stolen size check Vinod Govindapillai
2026-02-24 18:21   ` Shankar, Uma
2026-02-20 17:09 ` [PATCH v2 2/6] drm/i915/display: remove the usage of dev_priv Vinod Govindapillai
2026-02-24 13:17   ` Kahola, Mika
2026-02-20 17:09 ` [PATCH v2 3/6] drm/i915/fbdev: Extract intel_fbdev_fb_prefer_stolen() Vinod Govindapillai
2026-02-21 12:31   ` kernel test robot
2026-02-21 13:44   ` kernel test robot
2026-02-24 18:55   ` Shankar, Uma
2026-02-20 17:09 ` [PATCH v2 4/6] drm/xe/fbdev: " Vinod Govindapillai
2026-02-20 17:09 ` [PATCH v2 5/6] drm/xe/fbdev: print info about stolen memory preference for fbdev Vinod Govindapillai
2026-02-24 18:36   ` Shankar, Uma
2026-02-20 17:09 ` [PATCH v2 6/6] drm/i915/fbdev: " Vinod Govindapillai
2026-02-24 18:37   ` Shankar, Uma
2026-02-20 18:21 ` ✓ CI.KUnit: success for update the stolen memory allocation preference (rev2) Patchwork
2026-02-20 18:37 ` ✗ CI.checksparse: warning " Patchwork
2026-02-20 18:59 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-21  9:24 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-25 11:12 ` [PATCH v2 0/6] update the stolen memory allocation preference Kahola, Mika

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=20260220170908.201422-1-vinod.govindapillai@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@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