From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <saurabhg.gupta@intel.com>,
<alex.zuo@intel.com>, <matthew.brost@intel.com>,
<john.c.harrison@intel.com>
Subject: Re: [PATCH 0/2] drm/xe/xe_vm: Add error injection support to lock and prep
Date: Wed, 27 Aug 2025 09:26:44 -0400 [thread overview]
Message-ID: <aK8HlCbvZWlHEOzi@intel.com> (raw)
In-Reply-To: <20250826154352.90434-4-jonathan.cavitt@intel.com>
On Tue, Aug 26, 2025 at 03:43:53PM +0000, Jonathan Cavitt wrote:
> Error injection should use the error injection interface, and should be
> decoupled from CONFIG_DRM_XE_DEBUG. Remove TEST_VM_OPS_ERROR from the
> code, and add error injection support to the function
> vm_bind_ioctl_ops_lock_and_prep. This necessitates marking the function
> as noinline.
>
> Jonathan Cavitt (2):
> Revert "drm/xe: Add VM bind IOCTL error injection"
> drm/xe/xe_vm: Add error injection support to lock and prep
>
> drivers/gpu/drm/xe/xe_device_types.h | 12 -----------
> drivers/gpu/drm/xe/xe_pt.c | 12 -----------
> drivers/gpu/drm/xe/xe_vm.c | 31 ++++++----------------------
> drivers/gpu/drm/xe/xe_vm_types.h | 14 -------------
You used the wrong mailing list.
Please use intel-xe@lists.freedesktop.org for these.
keep intel-gfx@lists.freedesktop.org for i915 and display
related patches.
> 4 files changed, 6 insertions(+), 63 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-08-27 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 15:43 [PATCH 0/2] drm/xe/xe_vm: Add error injection support to lock and prep Jonathan Cavitt
2025-08-26 15:43 ` [PATCH 1/2] Revert "drm/xe: Add VM bind IOCTL error injection" Jonathan Cavitt
2025-08-27 3:36 ` Matthew Brost
2025-08-26 15:43 ` [PATCH 2/2] drm/xe/xe_vm: Add error injection support to lock and prep Jonathan Cavitt
2025-08-26 18:03 ` Matthew Brost
2025-08-26 18:34 ` Cavitt, Jonathan
2025-08-26 18:57 ` Matthew Brost
2025-08-26 16:44 ` ✓ i915.CI.BAT: success for " Patchwork
2025-08-26 17:51 ` [PATCH 0/2] " Cavitt, Jonathan
2025-08-27 2:28 ` ✗ i915.CI.Full: failure for " Patchwork
2025-08-27 13:26 ` Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-26 17:50 [PATCH 0/2] " Jonathan Cavitt
2025-08-27 4:25 ` Matthew Brost
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=aK8HlCbvZWlHEOzi@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=alex.zuo@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.brost@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 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.