From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Subject: Re: [PATCH] drm/xe/pf: Fix the address range assert in ggtt_get_pte helper
Date: Fri, 30 Jan 2026 23:11:15 +0100 [thread overview]
Message-ID: <5952b75a-8298-4b5b-a5e5-9287b14fae4b@intel.com> (raw)
In-Reply-To: <20260130215624.556099-1-michal.winiarski@intel.com>
On 1/30/2026 10:56 PM, Michał Winiarski wrote:
> The ggtt_get_pte helper used for saving VF GGTT incorrectly assumes that
> ggtt_size == ggtt_end.
> Fix it to avoid triggering spurious asserts if VF GGTT object lands in
> high GGTT range.
and now it matches assert in xe_ggtt_set_pte
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---> drivers/gpu/drm/xe/xe_ggtt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_ggtt.c b/drivers/gpu/drm/xe/xe_ggtt.c
> index 60665ad1415be..10bbf7a86b487 100644
> --- a/drivers/gpu/drm/xe/xe_ggtt.c
> +++ b/drivers/gpu/drm/xe/xe_ggtt.c
> @@ -193,7 +193,7 @@ static void xe_ggtt_set_pte_and_flush(struct xe_ggtt *ggtt, u64 addr, u64 pte)
> static u64 xe_ggtt_get_pte(struct xe_ggtt *ggtt, u64 addr)
> {
> xe_tile_assert(ggtt->tile, !(addr & XE_PTE_MASK));
> - xe_tile_assert(ggtt->tile, addr < ggtt->size);
> + xe_tile_assert(ggtt->tile, addr < ggtt->start + ggtt->size);
>
> return readq(&ggtt->gsm[addr >> XE_PTE_SHIFT]);
> }
next prev parent reply other threads:[~2026-01-30 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 21:56 [PATCH] drm/xe/pf: Fix the address range assert in ggtt_get_pte helper Michał Winiarski
2026-01-30 22:05 ` ✓ CI.KUnit: success for " Patchwork
2026-01-30 22:11 ` Michal Wajdeczko [this message]
2026-01-30 22:56 ` ✓ Xe.CI.BAT: " 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=5952b75a-8298-4b5b-a5e5-9287b14fae4b@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.winiarski@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