From: John Harrison <john.c.harrison@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/xe: Allow error injection for xe_pxp_exec_queue_add
Date: Thu, 4 Sep 2025 13:46:09 -0700 [thread overview]
Message-ID: <f7f09822-751f-4b50-b397-b50c4c6ed06c@intel.com> (raw)
In-Reply-To: <20250818234639.2965656-4-daniele.ceraolospurio@intel.com>
On 8/18/2025 4:46 PM, Daniele Ceraolo Spurio wrote:
> This will allow us to simulate this function returning an error like
> we do for other functions called in the exec_queue_create path.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/xe/xe_pxp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pxp.c b/drivers/gpu/drm/xe/xe_pxp.c
> index 3d62008c99f1..bdbdbbf6a678 100644
> --- a/drivers/gpu/drm/xe/xe_pxp.c
> +++ b/drivers/gpu/drm/xe/xe_pxp.c
> @@ -688,6 +688,7 @@ int xe_pxp_exec_queue_add(struct xe_pxp *pxp, struct xe_exec_queue *q)
>
> return ret;
> }
> +ALLOW_ERROR_INJECTION(xe_pxp_exec_queue_add, ERRNO);
>
> static void __pxp_exec_queue_remove(struct xe_pxp *pxp, struct xe_exec_queue *q, bool lock)
> {
next prev parent reply other threads:[~2025-09-04 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 23:46 [PATCH 1/2] drm/xe: Fix error handling if PXP fails to start Daniele Ceraolo Spurio
2025-08-18 23:46 ` [PATCH 2/2] drm/xe: Allow error injection for xe_pxp_exec_queue_add Daniele Ceraolo Spurio
2025-09-04 20:46 ` John Harrison [this message]
2025-08-19 0:18 ` ✗ CI.checkpatch: warning for series starting with [1/2] drm/xe: Fix error handling if PXP fails to start Patchwork
2025-08-19 0:19 ` ✓ CI.KUnit: success " Patchwork
2025-08-19 0:52 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-19 18:50 ` ✓ Xe.CI.Full: " Patchwork
2025-09-04 20:45 ` [PATCH 1/2] " John Harrison
2025-09-04 20:55 ` Daniele Ceraolo Spurio
2025-09-04 20:57 ` Daniele Ceraolo Spurio
2025-09-04 21:11 ` John Harrison
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=f7f09822-751f-4b50-b397-b50c4c6ed06c@intel.com \
--to=john.c.harrison@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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