From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com, alex.zuo@intel.com,
jonathan.cavitt@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,
matthew.brost@intel.com, maarten.lankhorst@linux.intel.com,
thomas.hellstrom@linux.intel.com, tzimmermann@suse.de
Subject: [PATCH v4 0/2] drm/xe/pagefault: Add SRCID to pagefault reporting
Date: Thu, 18 Jun 2026 23:33:10 +0800 [thread overview]
Message-ID: <20260618153312.877948-1-jonathan.cavitt@intel.com> (raw)
Add SRCID to the xe_pagefault struct, which reports the ID of the
faulting hardware unit. This will be passed on to the
xe_vm_get_property_ioctl for reading per-vm faults and will assist in
diagnosing pagefaults.
v2:
- Readd pad check, as the pad in the ioctl struct was not changed
(jcavitt)
v3:
- Rebase
v4:
- Squash SRCID with ASID to keep the struct compact (Matthew)
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 | 5 ++++-
drivers/gpu/drm/xe/xe_pagefault.c | 23 +++++++++++++++--------
drivers/gpu/drm/xe/xe_pagefault_types.h | 9 +++++++--
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, 38 insertions(+), 13 deletions(-)
--
2.53.0
next reply other threads:[~2026-06-18 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 15:33 Jonathan Cavitt [this message]
2026-06-18 15:33 ` [PATCH v4 1/2] drm/xe/pagefault: Add SRCID to pagefault struct Jonathan Cavitt
2026-06-18 15:45 ` sashiko-bot
2026-06-18 15:33 ` [PATCH v4 2/2] drm/xe/vm: Add srcid to xe_vm_get_property_ioctl fault report Jonathan Cavitt
2026-06-18 15:40 ` ✓ CI.KUnit: success for drm/xe/pagefault: Add SRCID to pagefault reporting (rev4) Patchwork
2026-06-18 16:31 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-18 23:40 ` ✓ 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=20260618153312.877948-1-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@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=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.