From: Matthew Brost <matthew.brost@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: <dri-devel@lists.freedesktop.org>, <saurabhg.gupta@intel.com>,
<alex.zuo@intel.com>, <mripard@kernel.org>, <airlied@gmail.com>,
<simona@ffwll.ch>, <linux-kernel@vger.kernel.org>,
<intel-xe@lists.freedesktop.org>, <Rodrigo.vivi@intel.com>,
<maarten.lankhorst@linux.intel.com>,
<thomas.hellstrom@linux.intel.com>, <tzimmermann@suse.de>
Subject: Re: [PATCH v3 0/2] drm/xe/pagefault: Add SRCID to pagefault reporting
Date: Wed, 17 Jun 2026 16:30:09 -0700 [thread overview]
Message-ID: <ajMuAc9qWxnvT7HJ@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260617181849.769247-1-jonathan.cavitt@intel.com>
On Thu, Jun 18, 2026 at 02:18:46AM +0800, Jonathan Cavitt wrote:
> Add SRCID to the xe_pagefault struct, which reports the ID of the
> faulting hardware unit. This will be passed on to the
So is this the EU ID?
> xe_vm_get_property_ioctl for reading per-vm faults and will assist in
> diagnosing pagefaults.
>
Is anyone asking for this? I'm wondering as this will conflict with one
of my series that is inflight upstream and believe is merged in some
internal branches.
Matt
> v2:
> - Readd pad check, as the pad in the ioctl struct was not changed
> (jcavitt)
>
> v3:
> - Rebase
>
> Jonathan Cavitt (2):
> drm/xe/pagefault: Add SRCID to pagefault struct
> drm/xe/vm: Add srcid to xe_vm_get_property_ioctl fault report
>
> drivers/gpu/drm/xe/xe_guc_pagefault.c | 1 +
> drivers/gpu/drm/xe/xe_pagefault.c | 6 ++++--
> drivers/gpu/drm/xe/xe_pagefault_types.h | 4 +++-
> drivers/gpu/drm/xe/xe_vm.c | 8 ++++++++
> drivers/gpu/drm/xe/xe_vm_types.h | 2 ++
> include/uapi/drm/xe_drm.h | 4 ++--
> 6 files changed, 20 insertions(+), 5 deletions(-)
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-06-17 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 18:18 [PATCH v3 0/2] drm/xe/pagefault: Add SRCID to pagefault reporting Jonathan Cavitt
2026-06-17 18:18 ` [PATCH v3 1/2] drm/xe/pagefault: Add SRCID to pagefault struct Jonathan Cavitt
2026-06-17 18:18 ` [PATCH v3 2/2] drm/xe/vm: Add srcid to xe_vm_get_property_ioctl fault report Jonathan Cavitt
2026-06-17 18:26 ` ✓ CI.KUnit: success for drm/xe/pagefault: Add SRCID to pagefault reporting (rev3) Patchwork
2026-06-17 19:06 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-17 23:30 ` Matthew Brost [this message]
2026-06-18 5:17 ` ✗ Xe.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=ajMuAc9qWxnvT7HJ@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=Rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=alex.zuo@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=saurabhg.gupta@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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