From: Francois Dugast <francois.dugast@intel.com>
To: <priyanka.dandamudi@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/xe_fault_injection: Inject error for xe_sync_entry_parse
Date: Thu, 20 Feb 2025 20:55:46 +0100 [thread overview]
Message-ID: <Z7eIwhjplr2feVr8@fdugast-desk> (raw)
In-Reply-To: <20250212090448.3068963-1-priyanka.dandamudi@intel.com>
On Wed, Feb 12, 2025 at 09:04:48AM +0000, priyanka.dandamudi@intel.com wrote:
> From: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
>
> This will make xe_sync_entry_parse function fail to cover the unexplored
> path while executing xe_vm_create_ioctl().
>
> Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
Reviewed-by: Francois Dugast <francois.dugast@intel.com>
> ---
> tests/intel/xe_fault_injection.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
> index 7ae941367..ede483535 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -263,6 +263,7 @@ simple_vm_bind(int fd, uint32_t vm)
> * @xe_pt_update_ops_prepare: xe_pt_update_ops_prepare
> * @xe_pt_update_ops_run: xe_pt_update_ops_run
> * @xe_vma_ops_alloc: xe_vma_ops_alloc
> + * @xe_sync_entry_parse: xe_sync_entry_parse
> */
> static void
> vm_bind_fail(int fd, const char function_name[])
> @@ -315,6 +316,7 @@ igt_main
> { "xe_pt_update_ops_prepare" },
> { "xe_pt_update_ops_run" },
> { "xe_vma_ops_alloc" },
> + { "xe_sync_entry_parse" },
> { }
> };
>
> --
> 2.34.1
>
prev parent reply other threads:[~2025-02-20 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 9:04 [PATCH i-g-t] tests/xe_fault_injection: Inject error for xe_sync_entry_parse priyanka.dandamudi
2025-02-12 10:09 ` ✓ i915.CI.BAT: success for " Patchwork
2025-02-12 10:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-12 14:24 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-12 15:25 ` ✗ i915.CI.Full: " Patchwork
2025-02-20 19:55 ` Francois Dugast [this message]
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=Z7eIwhjplr2feVr8@fdugast-desk \
--to=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=priyanka.dandamudi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox