All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Andrew Zhou" <zhoulol888@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe/display: Remove invalid initial plane PTE check for iGPU
Date: Sat, 05 Sep 2026 14:36:26 +0000	[thread overview]
Message-ID: <20260905143626.E9C6B1F00A3E@smtp.kernel.org> (raw)
In-Reply-To: <20260905142500.17666-1-zhoulol888@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch removes the validation from the integrated graphics path, rendering the `has_lmembar()` logic completely dead and meaningless.
--

commit b290f7e32abe43d35ac4f5def3b10e9bcf641a88
Author: Andrew Zhou <zhoulol888@gmail.com>

drm/xe/display: Remove invalid initial plane PTE check for iGPU

This commit removes the initial plane PTE local memory validation for
integrated graphics, as Pantherlake can have the XE_GGTT_PTEDM bit set.
The check was causing a failure to create the initial framebuffer.

> diff --git a/drivers/gpu/drm/xe/display/xe_initial_plane.c b/drivers/gpu/drm/xe/display/xe_initial_plane.c
> index 0f86b73036d03..8c95dc4e6f2ef 100644
> --- a/drivers/gpu/drm/xe/display/xe_initial_plane.c
> +++ b/drivers/gpu/drm/xe/display/xe_initial_plane.c

[ ... ]

> @@ -93,13 +92,6 @@ initial_plane_bo(struct xe_device *xe,
>  			return NULL;
>  		}
>  
> -		pte = xe_ggtt_read_pte(tile0->mem.ggtt, base);
> -
> -		if (is_pte_local(pte) != need_pte_local(xe)) {
> -			drm_err(&xe->drm, "Initial plane PTE has bad local memory bit\n");
> -			return NULL;
> -		}
> -

[Severity: Low]
Does this leave need_pte_local() with dead logic?

By removing this validation from the integrated graphics path (!IS_DGFX(xe)),
the only remaining caller of need_pte_local() is inside the earlier 
if (IS_DGFX(xe)) branch in initial_plane_bo().

Because need_pte_local() is defined as:

static bool need_pte_local(struct xe_device *xe)
{
	return IS_DGFX(xe) || has_lmembar(xe);
}

It will now unconditionally evaluate to true when called, rendering the
has_lmembar(xe) check completely meaningless. 

Should need_pte_local() and its underlying logic be simplified or removed 
as well to prevent confusion?

>  		phys_base = base;
>  		flags |= XE_BO_FLAG_STOLEN;
>

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260905142500.17666-1-zhoulol888@gmail.com?part=1

  reply	other threads:[~2026-09-05 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 14:25 [PATCH] drm/xe/display: Remove invalid initial plane PTE check for iGPU Andrew Zhou
2026-09-05 14:36 ` sashiko-bot [this message]
2026-09-08 18:38 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2026-09-08 19:42 ` Patchwork
2026-09-15  6:42 ` [PATCH v2] " Andrew Zhou
2026-09-15  8:40   ` Jani Nikula
2026-09-15 13:59     ` Activate Windows
2026-09-18 13:54       ` Activate Windows
2026-09-15 14:14 ` ✗ LGCI.VerificationFailed: failure for drm/xe/display: Remove invalid initial plane PTE check for iGPU (rev2) Patchwork
2026-09-15 18:08 ` Patchwork
2026-09-23  6:59 ` ✓ i915.CI.BAT: success for drm/xe/display: Remove invalid initial plane PTE check for iGPU (rev3) Patchwork
2026-09-23 23:01 ` ✗ i915.CI.Full: failure " Patchwork

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=20260905143626.E9C6B1F00A3E@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zhoulol888@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.