Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: <igt-dev@lists.freedesktop.org>, <saurabhg.gupta@intel.com>,
	<alex.zuo@intel.com>, <michal.mrozek@intel.com>
Subject: Re: [PATCH i-g-t] include/drm-uapi/xe_drm: Add srcid to drm_xe_fault struct
Date: Wed, 03 Jun 2026 11:42:41 -0700	[thread overview]
Message-ID: <87ik7z79em.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87jysf7d3y.wl-ashutosh.dixit@intel.com>

On Wed, 03 Jun 2026 10:22:41 -0700, Dixit, Ashutosh wrote:
>
> On Wed, 03 Jun 2026 08:01:22 -0700, Jonathan Cavitt wrote:
> >
> > Add srcid to drm_xe_fault struct, aligning with a KMD change.
> > Additionally, add logging for the new information to the associated
> > xe_vm test.
>
> Please follow the format of previous commit messages to
> include/drm-uapi/xe_drm.h and include the kernel commit sha
> include/drm-uapi/xe_drm.h is being sync'd till.

What I mean is, no point sending the IGT patch for this till the kernel
patch is merged, anyway 'Test-with' doesn't work for Xe. And, after kernel
patch is merged, rather than just this change, the IGT uapi header should
be sync'd with the kernel uapi header using

	make INSTALL_HDR_PATH=<dest-dir> headers_install

>
> >
> > Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> > Cc: Michal Mrozek <michal.mrozek@intel.com>
> > ---
> >  include/drm-uapi/xe_drm.h | 4 ++--
> >  tests/intel/xe_vm.c       | 1 +
> >  2 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
> > index 5a96a7910b..273bac9e1f 100644
> > --- a/include/drm-uapi/xe_drm.h
> > +++ b/include/drm-uapi/xe_drm.h
> > @@ -1290,8 +1290,8 @@ struct xe_vm_fault {
> >  #define FAULT_LEVEL_PML4	3
> >  #define FAULT_LEVEL_PML5	4
> >	__u8 fault_level;
> > -	/** @pad: MBZ */
> > -	__u8 pad;
> > +	/** @srcid: ID of the faulting hardware unit */
> > +	__u8 srcid;
> >	/** @reserved: MBZ */
> >	__u64 reserved[4];
> >  };
> > diff --git a/tests/intel/xe_vm.c b/tests/intel/xe_vm.c
> > index 408bfdb718..260dae9cae 100644
> > --- a/tests/intel/xe_vm.c
> > +++ b/tests/intel/xe_vm.c
> > @@ -3023,6 +3023,7 @@ static void print_pf(struct xe_vm_fault *fault)
> >	igt_debug("access type = %u\n", fault->access_type);
> >	igt_debug("fault type = %u\n", fault->fault_type);
> >	igt_debug("fault level = %u\n", fault->fault_level);
> > +	igt_debug("srcid = 0x%08x\n", fault->srcid);
> >	igt_debug("\n");
> >  }
> >
> > --
> > 2.53.0
> >

  reply	other threads:[~2026-06-03 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 15:01 [PATCH i-g-t] include/drm-uapi/xe_drm: Add srcid to drm_xe_fault struct Jonathan Cavitt
2026-06-03 16:58 ` ✓ i915.CI.BAT: success for " Patchwork
2026-06-03 16:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-03 17:22 ` [PATCH i-g-t] " Dixit, Ashutosh
2026-06-03 18:42   ` Dixit, Ashutosh [this message]
2026-06-04  4:00 ` ✗ Xe.CI.FULL: failure for " Patchwork
2026-06-04 14:20 ` ✗ i915.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=87ik7z79em.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=alex.zuo@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=michal.mrozek@intel.com \
    --cc=saurabhg.gupta@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