From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [RFC v1 1/1] drm/xe: Allow fault injection in vm create and vm bind IOCTLs
Date: Fri, 8 Nov 2024 15:10:13 -0500 [thread overview]
Message-ID: <Zy5wJSsG8ppPCg2A@intel.com> (raw)
In-Reply-To: <20241108161307.1203967-2-francois.dugast@intel.com>
On Fri, Nov 08, 2024 at 05:11:56PM +0100, Francois Dugast wrote:
> Use fault injection infrastructure to allow specific functions to
> be configured over debugfs for failing during the execution of
> xe_vm_create_ioctl() and xe_vm_bind_ioctl(). This allows more
> thorough testing from user space by going through code paths for
> error handling and unwinding which cannot be reached by simply
> injecting errors in IOCTL arguments. This can help increase code
> robustness.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_exec_queue.c | 1 +
> drivers/gpu/drm/xe/xe_pt.c | 1 +
> drivers/gpu/drm/xe/xe_vm.c | 4 ++++
> 3 files changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
> index fd0f3b3c9101..b999db5f5c19 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
> @@ -240,6 +240,7 @@ struct xe_exec_queue *xe_exec_queue_create_bind(struct xe_device *xe,
>
> return q;
> }
> +ALLOW_ERROR_INJECTION(xe_exec_queue_create_bind, ERRNO);
>
> void xe_exec_queue_destroy(struct kref *ref)
> {
> diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> index f27f579f4d85..e111698abbd9 100644
> --- a/drivers/gpu/drm/xe/xe_pt.c
> +++ b/drivers/gpu/drm/xe/xe_pt.c
> @@ -136,6 +136,7 @@ struct xe_pt *xe_pt_create(struct xe_vm *vm, struct xe_tile *tile,
> xe_pt_free(pt);
> return ERR_PTR(err);
> }
> +ALLOW_ERROR_INJECTION(xe_pt_create, ERRNO);
>
> /**
> * xe_pt_populate_empty() - Populate a page-table bo with scratch- or zero
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 624133fae5f5..2e67648ed512 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -740,6 +740,7 @@ static int xe_vma_ops_alloc(struct xe_vma_ops *vops, bool array_of_binds)
>
> return 0;
> }
> +ALLOW_ERROR_INJECTION(xe_vma_ops_alloc, ERRNO);
>
> static void xe_vma_ops_fini(struct xe_vma_ops *vops)
> {
> @@ -1352,6 +1353,7 @@ static int xe_vm_create_scratch(struct xe_device *xe, struct xe_tile *tile,
>
> return 0;
> }
> +ALLOW_ERROR_INJECTION(xe_vm_create_scratch, ERRNO);
>
> static void xe_vm_free_scratch(struct xe_vm *vm)
> {
> @@ -1978,6 +1980,7 @@ vm_bind_ioctl_ops_create(struct xe_vm *vm, struct xe_bo *bo,
>
> return ops;
> }
> +ALLOW_ERROR_INJECTION(vm_bind_ioctl_ops_create, ERRNO);
>
> static struct xe_vma *new_vma(struct xe_vm *vm, struct drm_gpuva_op_map *op,
> u16 pat_index, unsigned int flags)
> @@ -2697,6 +2700,7 @@ static int vm_bind_ioctl_ops_execute(struct xe_vm *vm,
> drm_exec_fini(&exec);
> return err;
> }
> +ALLOW_ERROR_INJECTION(vm_bind_ioctl_ops_execute, ERRNO);
>
> #define SUPPORTED_FLAGS_STUB \
> (DRM_XE_VM_BIND_FLAG_READONLY | \
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-11-08 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:11 [RFC v1 0/1] Allow fault injection in vm create and vm bind IOCTLs Francois Dugast
2024-11-08 16:11 ` [RFC v1 1/1] drm/xe: " Francois Dugast
2024-11-08 16:16 ` Matthew Brost
2024-11-08 17:20 ` Francois Dugast
2024-11-08 17:47 ` Matthew Brost
2024-11-08 20:10 ` Rodrigo Vivi [this message]
2024-11-12 11:14 ` Francois Dugast
2024-11-13 14:24 ` Rodrigo Vivi
2024-11-08 16:18 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-08 16:18 ` ✓ CI.checkpatch: " Patchwork
2024-11-08 16:19 ` ✓ CI.KUnit: " Patchwork
2024-11-08 16:31 ` ✓ CI.Build: " Patchwork
2024-11-08 16:33 ` ✓ CI.Hooks: " Patchwork
2024-11-08 16:35 ` ✓ CI.checksparse: " Patchwork
2024-11-08 16:52 ` ✓ CI.BAT: " Patchwork
2024-11-09 18:40 ` ✗ CI.FULL: failure " 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=Zy5wJSsG8ppPCg2A@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@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 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.