From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/xe/evict: drop bogus assert
Date: Fri, 10 Oct 2025 17:27:30 +0200 [thread overview]
Message-ID: <cdaa5a66610f230cdee70def4b90d975d3c1b734.camel@linux.intel.com> (raw)
In-Reply-To: <20251010152457.177884-2-matthew.auld@intel.com>
On Fri, 2025-10-10 at 16:24 +0100, Matthew Auld wrote:
> This assert can trigger here with non pin_map users that select
> LATE_RESTORE, since the vmap is allowed to be NULL given that
> save/restore can now use the blitter instead. The check here doesn't
> seem to have much value anymore given that we no longer move pinned
> memory, so any existing vmap is left well alone, and doesn't need to
> be
> recreated upon restore, so just drop the assert here.
>
> Fixes: 86f69c26113c ("drm/xe: use backup object for pinned
> save/restore")
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6213
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/xe/xe_bo_evict.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_bo_evict.c
> b/drivers/gpu/drm/xe/xe_bo_evict.c
> index 1a12675b2ea9..7661fca7f278 100644
> --- a/drivers/gpu/drm/xe/xe_bo_evict.c
> +++ b/drivers/gpu/drm/xe/xe_bo_evict.c
> @@ -191,7 +191,6 @@ int xe_bo_evict_all(struct xe_device *xe)
>
> static int xe_bo_restore_and_map_ggtt(struct xe_bo *bo)
> {
> - struct xe_device *xe = xe_bo_device(bo);
> int ret;
>
> ret = xe_bo_restore_pinned(bo);
> @@ -210,13 +209,6 @@ static int xe_bo_restore_and_map_ggtt(struct
> xe_bo *bo)
> }
> }
>
> - /*
> - * We expect validate to trigger a move VRAM and our move
> code
> - * should setup the iosys map.
> - */
> - xe_assert(xe, !(bo->flags & XE_BO_FLAG_PINNED_LATE_RESTORE)
> ||
> - !iosys_map_is_null(&bo->vmap));
> -
> return 0;
> }
>
next prev parent reply other threads:[~2025-10-10 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 15:24 [PATCH] drm/xe/evict: drop bogus assert Matthew Auld
2025-10-10 15:27 ` Thomas Hellström [this message]
2025-10-10 15:32 ` ✓ CI.KUnit: success for " Patchwork
2025-10-10 16:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-10 21:55 ` ✓ Xe.CI.Full: " 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=cdaa5a66610f230cdee70def4b90d975d3c1b734.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@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