tree 10f3b32e47d56e9433010b30e6825a886cc9f80a
parent b320789d6883cc00ac78ce83bccbfe7ed58afcf0
author Thomas Hellström <thomas.hellstrom@linux.intel.com> 1756388917 +0200
committer Rodrigo Vivi <rodrigo.vivi@intel.com> 1756818047 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEbSBwaO7dZQkcLOKj+mJfZA7rE8oFAmi26n8ACgkQ+mJfZA7r
 E8o/Cgf/ZGeB4TwCp4DGAR1rggl+KNa0iIWL0g61ge3EJzTqVxyPpdztWbbeg7O0
 JXVHPI62oA9XQiVhqZyqbLUEzuxHC9SWn3FTjB7bElzY3Isztm9c+gT4C4lN+Khm
 M4RbxOO4RoggvsrXkcjDv0PqjToiz58U8+mwEZ34HiGUiWx5C/5eDY5z4SY6dA5m
 FhMAbcKgje1ZRHciUuiqn1n/LBXwkdOZG347QLQL/WwEs56SjZyUt5eqA2GNI6aR
 ahU3jT017VmwZ7N1CtZUIOwwdvv2dFMcGVN8FUiqOg7C1eAgSlN1ZGqBuDEilyeB
 PKo/Qp3nxsa8O4BOB1eYMCv6vXVoww==
 =TvpH
 -----END PGP SIGNATURE-----

drm/xe: Fix incorrect migration of backed-up object to VRAM

If an object is backed up to shmem it is incorrectly identified
as not having valid data by the move code. This means moving
to VRAM skips the -EMULTIHOP step and the bo is cleared. This
causes all sorts of weird behaviour on DGFX if an already evicted
object is targeted by the shrinker.

Fix this by using ttm_tt_is_swapped() to identify backed-up
objects.

Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/5996
Fixes: 00c8efc3180f ("drm/xe: Add a shrinker for xe bos")
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: <stable@vger.kernel.org> # v6.15+
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://lore.kernel.org/r/20250828134837.5709-1-thomas.hellstrom@linux.intel.com
(cherry picked from commit 1047bd82794a1eab64d643f196d09171ce983f44)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>