From: "Sharma, Nishit" <nishit.sharma@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
igt-dev@lists.freedesktop.org
Cc: Francois Dugast <francois.dugast@intel.com>
Subject: Re: [PATCH i-g-t v4 0/5] Extend compute userenv to support user passed buffers
Date: Tue, 3 Mar 2026 20:26:18 +0530 [thread overview]
Message-ID: <d99df782-2a3c-4189-975a-a39d0d2fbf6f@intel.com> (raw)
In-Reply-To: <20260303134706.41948-7-zbigniew.kempczynski@intel.com>
Hi,
Can we have description like:
This patch series enhances the compute test coverage in IGT by
introducing new subtests for compute workload.
The new subtests exercise various buffer allocation and mapping
strategies, including classic buffer objects (BOs),
user environment (userenv) buffers, and system-allocated (SVM) buffers.
Otherwise LGTM
Acked-by: Nishit Sharma <nishit.sharma@intel.com>
On 3/3/2026 7:17 PM, Zbigniew Kempczyński wrote:
> Add support for user passed buffers in compute userenv. This allows
> users to pass their own input and output buffers to compute tests, which
> can be useful for testing specific scenarios.
>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Cc: Nishit Sharma <nishit.sharma@intel.com>
>
> Zbigniew Kempczyński (4):
> lib/intel_compute: Add types for input and output buffers
> lib/intel_compute: Extend userenv by adding input and output bos
> lib/intel_compute: Use user offsets and loop size if provided
> tests/xe_compute: Exercise user passed buffers
> tests/xe_compute: Use appropriate feature in compute-square tests
>
> lib/intel_compute.c | 191 ++++++++++++++++++++++++++++-----------
> lib/intel_compute.h | 4 +
> tests/intel/xe_compute.c | 154 ++++++++++++++++++++++++++++++-
> 3 files changed, 294 insertions(+), 55 deletions(-)
>
next prev parent reply other threads:[~2026-03-03 14:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 13:47 [PATCH i-g-t v4 0/5] Extend compute userenv to support user passed buffers Zbigniew Kempczyński
2026-03-03 13:47 ` [PATCH i-g-t v4 1/5] lib/intel_compute: Add types for input and output buffers Zbigniew Kempczyński
2026-03-03 13:47 ` [PATCH i-g-t v4 2/5] lib/intel_compute: Extend userenv by adding input and output bos Zbigniew Kempczyński
2026-03-03 13:47 ` [PATCH i-g-t v4 3/5] lib/intel_compute: Use user offsets and loop size if provided Zbigniew Kempczyński
2026-03-03 15:07 ` Sharma, Nishit
2026-03-03 16:37 ` Kamil Konieczny
2026-03-03 18:30 ` Sharma, Nishit
2026-03-04 7:56 ` Zbigniew Kempczyński
2026-03-03 16:31 ` Kamil Konieczny
2026-03-03 13:47 ` [PATCH i-g-t v4 4/5] tests/xe_compute: Exercise user passed buffers Zbigniew Kempczyński
2026-03-03 13:47 ` [PATCH i-g-t v4 5/5] tests/xe_compute: Use appropriate feature in compute-square tests Zbigniew Kempczyński
2026-03-03 14:56 ` Sharma, Nishit [this message]
2026-03-04 7:59 ` [PATCH i-g-t v4 0/5] Extend compute userenv to support user passed buffers Zbigniew Kempczyński
2026-03-04 3:24 ` ✓ Xe.CI.BAT: success for Extend compute userenv to support user passed buffers (rev4) Patchwork
2026-03-04 3:45 ` ✓ i915.CI.BAT: " Patchwork
2026-03-05 0:46 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-05 5:58 ` ✗ i915.CI.Full: " 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=d99df782-2a3c-4189-975a-a39d0d2fbf6f@intel.com \
--to=nishit.sharma@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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