Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"DRM XE List" <intel-xe@lists.freedesktop.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the drm-xe tree with the mm-unstable tree
Date: Wed, 25 Feb 2026 11:19:50 +0000	[thread overview]
Message-ID: <aZ7a1vc2xSClNEZi@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2971 bytes --]

Hi all,

Today's linux-next merge of the drm-xe tree got a conflict in:

  mm/migrate_device.c

between commit:

  1de80c790c979 ("mm/migrate_device: remove dead migration entry check in migrate_vma_collect_huge_pmd()")

from the mm-unstable tree and commit:

  a69d1ab971a62 ("mm: Fix a hmm_range_fault() livelock / starvation problem")

from the drm-xe tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --combined mm/migrate_device.c
index 78c7acf024615,deab89fd45419..0000000000000
--- a/mm/migrate_device.c
+++ b/mm/migrate_device.c
@@@ -175,6 -175,12 +175,6 @@@ static int migrate_vma_collect_huge_pmd
  			return migrate_vma_collect_skip(start, end, walk);
  		}
  
 -		if (softleaf_is_migration(entry)) {
 -			softleaf_entry_wait_on_locked(entry, ptl);
 -			spin_unlock(ptl);
 -			return -EAGAIN;
 -		}
 -
  		if (softleaf_is_device_private_write(entry))
  			write = MIGRATE_PFN_WRITE;
  	} else {
@@@ -265,7 -271,7 +265,7 @@@ again
  	ptep = pte_offset_map_lock(mm, pmdp, start, &ptl);
  	if (!ptep)
  		goto again;
 -	arch_enter_lazy_mmu_mode();
 +	lazy_mmu_mode_enable();
  	ptep += (addr - start) / PAGE_SIZE;
  
  	for (; addr < end; addr += PAGE_SIZE, ptep++) {
@@@ -307,7 -313,7 +307,7 @@@
  			if (folio_test_large(folio)) {
  				int ret;
  
 -				arch_leave_lazy_mmu_mode();
 +				lazy_mmu_mode_disable();
  				pte_unmap_unlock(ptep, ptl);
  				ret = migrate_vma_split_folio(folio,
  							  migrate->fault_page);
@@@ -350,7 -356,7 +350,7 @@@
  			if (folio && folio_test_large(folio)) {
  				int ret;
  
 -				arch_leave_lazy_mmu_mode();
 +				lazy_mmu_mode_disable();
  				pte_unmap_unlock(ptep, ptl);
  				ret = migrate_vma_split_folio(folio,
  							  migrate->fault_page);
@@@ -479,7 -485,7 +479,7 @@@ next
  	if (unmapped)
  		flush_tlb_range(walk->vma, start, end);
  
 -	arch_leave_lazy_mmu_mode();
 +	lazy_mmu_mode_disable();
  	pte_unmap_unlock(ptep - 1, ptl);
  
  	return 0;
@@@ -1413,10 -1419,10 +1413,10 @@@ EXPORT_SYMBOL(migrate_device_range)
  
  /**
   * migrate_device_pfns() - migrate device private pfns to normal memory.
 - * @src_pfns: pre-popluated array of source device private pfns to migrate.
 + * @src_pfns: pre-populated array of source device private pfns to migrate.
   * @npages: number of pages to migrate.
   *
 - * Similar to migrate_device_range() but supports non-contiguous pre-popluated
 + * Similar to migrate_device_range() but supports non-contiguous pre-populated
   * array of device pages to migrate.
   */
  int migrate_device_pfns(unsigned long *src_pfns, unsigned long npages)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-02-25 11:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aZ7a1vc2xSClNEZi@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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