Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Uma Shankar <uma.shankar@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	daniele.ceraolospurio@intel.com, vinay.belgaumkar@intel.com
Subject: Re: [PATCH] drm/xe/fbdev: Limit the usage of stolen for LNL+
Date: Thu, 11 Jul 2024 20:38:35 +0300	[thread overview]
Message-ID: <ZpAYm0w5DA9bfo-1@intel.com> (raw)
In-Reply-To: <phpidsyio6aub43cbfdcll44k7rrh73chqsuktraenzx6575af@645b423aaz6q>

On Thu, Jul 11, 2024 at 11:31:54AM -0500, Lucas De Marchi wrote:
> On Thu, Jul 11, 2024 at 10:43:39AM GMT, Uma Shankar wrote:
> >As per recommendation in the workarounds:
> >WA_14021987551, Wa_16023588340:
> >
> >There is an issue with accessing Stolen memory pages due a
> >hardware limitation. Limit the usage of stolen memory for
> >fbdev for LNL+. Don't use BIOS FB from stolen on LNL+ and
> >assign the same from system memory.
> >
> >Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> >---
> > drivers/gpu/drm/xe/display/intel_fbdev_fb.c   | 10 +++++++++-
> > drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 ++++++++++
> > 2 files changed, 19 insertions(+), 1 deletion(-)
> >
> >diff --git a/drivers/gpu/drm/xe/display/intel_fbdev_fb.c b/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> >index 816ad13821a8..8fda8745ce0a 100644
> >--- a/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> >+++ b/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> >@@ -37,7 +37,14 @@ struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_fb_helper *helper,
> > 	size = PAGE_ALIGN(size);
> > 	obj = ERR_PTR(-ENODEV);
> >
> >-	if (!IS_DGFX(xe)) {
> >+	/*
> >+	 * WA_14021987551, Wa_16023588340:
> 
> not the proper way to handle WAs in xe. Please use XE_WA()
> 
> 
> >+	 * There is an issue with accessing Stolen memory pages
> >+	 * due a hardware limitation. Limit the usage of stolen
> >+	 * memory for fbdev for LNL+. Don't use BIOS FB from
> >+	 * stolen on LNL+ and assign the same from system memory
> 
> I wonder if we can't simply set to 0 the available stolen space after the
> places that really need it already had their allocation done.

FBC needs stolen.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-07-11 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  5:13 [PATCH] drm/xe/fbdev: Limit the usage of stolen for LNL+ Uma Shankar
2024-07-11  5:11 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-11  5:11 ` ✓ CI.checkpatch: " Patchwork
2024-07-11  5:12 ` ✓ CI.KUnit: " Patchwork
2024-07-11  5:24 ` ✓ CI.Build: " Patchwork
2024-07-11  5:26 ` ✓ CI.Hooks: " Patchwork
2024-07-11  5:28 ` ✓ CI.checksparse: " Patchwork
2024-07-11  5:52 ` ✓ CI.BAT: " Patchwork
2024-07-11  6:52 ` ✗ CI.FULL: failure " Patchwork
2024-07-11 16:31 ` [PATCH] " Lucas De Marchi
2024-07-11 17:38   ` Ville Syrjälä [this message]
2024-07-14 19:41   ` Shankar, Uma
2024-07-11 16:37 ` Matt Roper
2024-07-11 17:06   ` Lucas De Marchi
2024-07-14 19:49     ` Shankar, Uma
2024-07-14 19:46   ` Shankar, Uma

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=ZpAYm0w5DA9bfo-1@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=uma.shankar@intel.com \
    --cc=vinay.belgaumkar@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