Linux-Next discussions
 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: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Matt Roper <matthew.d.roper@intel.com>,
	Raag Jadav <raag.jadav@intel.com>,
	Riana Tauro <riana.tauro@intel.com>
Subject: linux-next: manual merge of the drm-xe tree with the drm-fixes tree
Date: Fri, 14 Aug 2026 17:12:44 +0100	[thread overview]
Message-ID: <an8-fFKBQKlJ3tQ1@sirena.org.uk> (raw)

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

Hi all,

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

  drivers/gpu/drm/xe/xe_device.c

between commit:

  ef526d122b62a ("drm/xe: Fix xe_device_probe() failure")

from the drm-fixes tree and commits:

  5ce3042c67c53 ("drm/xe: Fix xe_device_probe() failure")
  20bc4883c7c0e ("drm/xe/ras: Fix boot-time ras error processing")

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 drivers/gpu/drm/xe/xe_device.c
index 2bf38a7684c64,71111ad324658..0000000000000
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@@ -282,7 -282,7 +282,7 @@@ static vm_fault_t barrier_fault(struct 
  	pgprot_t prot;
  	int idx;
  
 -	prot = vm_get_page_prot(vma->vm_flags);
 +	prot = vma_get_page_prot(vma);
  
  	if (drm_dev_enter(dev, &idx)) {
  		unsigned long pfn;
@@@ -331,7 -331,7 +331,7 @@@ static int xe_pci_barrier_mmap(struct f
  	if (vma->vm_end - vma->vm_start > SZ_4K)
  		return -EINVAL;
  
 -	if (is_cow_mapping(vma->vm_flags))
 +	if (vma_is_cow_mapping(vma))
  		return -EINVAL;
  
  	if (vma->vm_flags & (VM_READ | VM_EXEC))
@@@ -513,6 -513,17 +513,17 @@@ struct xe_device *xe_device_create(stru
  }
  ALLOW_ERROR_INJECTION(xe_device_create, ERRNO); /* See xe_pci_probe() */
  
+ static void xe_device_parse_modparam(struct xe_device *xe)
+ {
+ 	xe->atomic_svm_timeslice_ms = 5;
+ 	xe->min_run_period_lr_ms = 5;
+ 	xe->info.num_pf_work = xe_modparam.num_pf_work;
+ 	if (xe->info.num_pf_work < 1)
+ 		xe->info.num_pf_work = 1;
+ 	else if (xe->info.num_pf_work > XE_PAGEFAULT_WORK_MAX)
+ 		xe->info.num_pf_work = XE_PAGEFAULT_WORK_MAX;
+ }
+ 
  /**
   * xe_device_init_early() - Initialize a new &xe_device instance
   * @xe: the &xe_device to initialize
@@@ -539,8 -550,7 +550,7 @@@ int xe_device_init_early(struct xe_devi
  	if (err)
  		return err;
  
- 	xe->atomic_svm_timeslice_ms = 5;
- 	xe->min_run_period_lr_ms = 5;
+ 	xe_device_parse_modparam(xe);
  
  	err = xe_irq_init(xe);
  	if (err)
@@@ -1141,6 -1151,13 +1151,13 @@@ int xe_device_probe(struct xe_device *x
  	if (err)
  		goto err_unregister_display;
  
+ 	/*
+ 	 * Process and log any errors detected by hardware. Possible results can
+ 	 * include declaring the device as wedged, which must be done only after
+ 	 * xe_device_wedged_fini() is registered.
+ 	 */
+ 	xe_ras_process_errors(xe);
+ 
  	err = devm_add_action_or_reset(xe->drm.dev, xe_device_sanitize, xe);
  	if (err)
  		goto err_unregister_display;

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

             reply	other threads:[~2026-08-14 16:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 16:12 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-18 12:31 linux-next: manual merge of the drm-xe tree with the drm-fixes tree Mark Brown
2026-07-03 16:20 Mark Brown
2026-07-03 15:44 Mark Brown
2026-07-03 15:44 Mark Brown
2026-07-03 15:41 Mark Brown
2026-07-03 15:41 Mark Brown
2026-01-30 16:05 Mark Brown
2026-01-23 15:34 Mark Brown
2025-09-19 12:49 Mark Brown
2025-09-19 12:45 Mark Brown
2025-09-22 18:28 ` Nathan Chancellor
2025-09-22 19:25   ` Lucas De Marchi
2024-12-06 12:55 Mark Brown

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=an8-fFKBQKlJ3tQ1@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthew.d.roper@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --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