From: Matthew Brost <matthew.brost@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] Revert "drm/pagemap: Disable device-to-device migration"
Date: Wed, 11 Feb 2026 10:21:29 -0800 [thread overview]
Message-ID: <aYzIqRB6yDKDkejE@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20260211104159.114947-1-thomas.hellstrom@linux.intel.com>
On Wed, Feb 11, 2026 at 11:41:59AM +0100, Thomas Hellström wrote:
> With commit
> a69d1ab971a6 ("mm: Fix a hmm_range_fault() livelock / starvation problem")
> device-to-device migration is not functional again and the
> disabling can be reverted.
>
> Add the above commit as a Fixes: tag in order for the revert to not
> take place unless that commit is present.
>
> This reverts commit 10dd1eaa80a56d3cf6d7c36b5269c8fed617f001.
>
> Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Fixes: a69d1ab971a6 ("mm: Fix a hmm_range_fault() livelock / starvation problem")
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/drm_pagemap.c | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_pagemap.c b/drivers/gpu/drm/drm_pagemap.c
> index 38eca94f01a1..73438ba275bc 100644
> --- a/drivers/gpu/drm/drm_pagemap.c
> +++ b/drivers/gpu/drm/drm_pagemap.c
> @@ -480,18 +480,8 @@ int drm_pagemap_migrate_to_devmem(struct drm_pagemap_devmem *devmem_allocation,
> .start = start,
> .end = end,
> .pgmap_owner = pagemap->owner,
> - /*
> - * FIXME: MIGRATE_VMA_SELECT_DEVICE_PRIVATE intermittently
> - * causes 'xe_exec_system_allocator --r *race*no*' to trigger aa
> - * engine reset and a hard hang due to getting stuck on a folio
> - * lock. This should work and needs to be root-caused. The only
> - * downside of not selecting MIGRATE_VMA_SELECT_DEVICE_PRIVATE
> - * is that device-to-device migrations won’t work; instead,
> - * memory will bounce through system memory. This path should be
> - * rare and only occur when the madvise attributes of memory are
> - * changed or atomics are being used.
> - */
> - .flags = MIGRATE_VMA_SELECT_SYSTEM | MIGRATE_VMA_SELECT_DEVICE_COHERENT,
> + .flags = MIGRATE_VMA_SELECT_SYSTEM | MIGRATE_VMA_SELECT_DEVICE_COHERENT |
> + MIGRATE_VMA_SELECT_DEVICE_PRIVATE,
> };
> unsigned long i, npages = npages_in_range(start, end);
> unsigned long own_pages = 0, migrated_pages = 0;
> --
> 2.52.0
>
prev parent reply other threads:[~2026-02-11 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 10:41 [PATCH] Revert "drm/pagemap: Disable device-to-device migration" Thomas Hellström
2026-02-11 10:50 ` ✓ CI.KUnit: success for " Patchwork
2026-02-11 11:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-11 14:03 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-11 18:21 ` Matthew Brost [this message]
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=aYzIqRB6yDKDkejE@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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