From: "Randhawa, Jagmeet" <jagmeet.randhawa@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>, <jonathan.cavitt@intel.com>,
<alex.zuo@intel.com>, <kamil.konieczny@intel.com>
Subject: Re: [PATCH] [i-g-t] tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs
Date: Tue, 5 Nov 2024 12:31:54 -0800 [thread overview]
Message-ID: <77e0cbd0-52ec-4c9a-838f-7cfc8ae74e37@intel.com> (raw)
In-Reply-To: <20241028165311.q7qlo65v5fo2xoz3@kamilkon-desk.igk.intel.com>
On 10/28/2024 9:53 AM, Kamil Konieczny wrote:
> Hi Jagmeet,
> On 2024-10-22 at 20:11:30 +0000, Jagmeet Randhawa wrote:
>
> small nit for subject, please place space after ':'
> [i-g-t] tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs
>
> should be:
>
> [i-g-t] tests/intel/xe_vm: Reduce n_execs for bind-array-enobufs
>
>> The bind-array-enobufs test in xe_vm.c is intended to trigger
>> an -ENOBUFS error by submitting an oversized bind array.
>> After encountering and handling the error, the test reduces
>> n_execs by half and retries the operation. On some environments
>> with stricter resource limits (e.g. simulator), halving
>> n_execs isn't sufficient to prevent the ENOBUFS error on the retry.
>> Reducing n_execs further to n_execs / 4 allows the test to pass
>> successfully. This patch modifies the test to reduce n_execs
> --------------- ^
> Imho you repeat your argument again here, I will take only
> what is up to 'This patch...' with Jonathan r-b.
>
> Also please replay to CI failure reports, I will do this now
> as to give you an example how to follow up with your next patches.
>
> Regards,
> Kamil
Hey Kamil, I have adjusted the patch according to your comments and sent
v2 just now. Thank you for the comments.
>> to n_execs / 4 after an ENOBUFS error is handled. This ensures
>> compatibility with environments that have tighter resource
>> constraints while maintaining the test's integrity.
>>
>> Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
>> Signed-off-by: Jagmeet Randhawa <jagmeet.randhawa@intel.com>
>> ---
>> tests/intel/xe_vm.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tests/intel/xe_vm.c b/tests/intel/xe_vm.c
>> index 7a8740b69..e78ddd0e5 100644
>> --- a/tests/intel/xe_vm.c
>> +++ b/tests/intel/xe_vm.c
>> @@ -957,7 +957,7 @@ test_bind_array(int fd, struct drm_xe_engine_class_instance *eci, int n_execs,
>> xe_cork_end(&cork);
>> xe_cork_wait_done(&cork);
>> xe_cork_fini(&cork);
>> - n_execs = n_execs / 2;
>> + n_execs = n_execs / 4;
>> }
>>
>> xe_vm_bind_array(fd, vm, bind_exec_queue, bind_ops, n_execs, sync, 1);
>> --
>> 2.34.1
>>
prev parent reply other threads:[~2024-11-05 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 20:11 [PATCH] [i-g-t] tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs Jagmeet Randhawa
2024-10-22 21:05 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-10-28 16:56 ` Kamil Konieczny
2024-10-22 21:46 ` ✓ CI.xeBAT: success " Patchwork
2024-10-23 4:37 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-28 16:55 ` Kamil Konieczny
2024-11-05 20:33 ` Randhawa, Jagmeet
2024-10-23 14:12 ` [PATCH] [i-g-t] " Cavitt, Jonathan
2024-10-23 20:29 ` Randhawa, Jagmeet
2024-10-23 20:35 ` Cavitt, Jonathan
2024-10-28 16:53 ` Kamil Konieczny
2024-11-05 20:31 ` Randhawa, Jagmeet [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=77e0cbd0-52ec-4c9a-838f-7cfc8ae74e37@intel.com \
--to=jagmeet.randhawa@intel.com \
--cc=alex.zuo@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=kamil.konieczny@intel.com \
--cc=kamil.konieczny@linux.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