From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH i-g-t v2 4/9] tests/intel/xe_create: Stop treating the extension field as MBZ
Date: Thu, 16 Jan 2025 22:02:31 +0000 [thread overview]
Message-ID: <7626a11d90ed144fce3125421632746059eceb68.camel@intel.com> (raw)
In-Reply-To: <20250116001951.4159243-5-daniele.ceraolospurio@intel.com>
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
On Wed, 2025-01-15 at 16:19 -0800, Daniele Ceraolo Spurio wrote:
> A new extension for the xe_create ioctl was added to support PXP, so the
> field is no longer expected to always be zero.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> ---
> tests/intel/xe_create.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/tests/intel/xe_create.c b/tests/intel/xe_create.c
> index 07e11036d..0907a8a8a 100644
> --- a/tests/intel/xe_create.c
> +++ b/tests/intel/xe_create.c
> @@ -127,11 +127,6 @@ static void create_invalid_mbz(int fd)
> gem_close(fd, create.handle);
> create.handle = 0;
>
> - /* No supported extensions yet */
> - create.extensions = -1;
> - igt_assert_eq(__ioctl_create(fd, &create), -EINVAL);
> - create.extensions = 0;
> -
> /* Make sure KMD rejects non-zero padding/reserved fields */
> for (i = 0; i < ARRAY_SIZE(create.pad); i++) {
> create.pad[i] = -1;
next prev parent reply other threads:[~2025-01-16 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 0:19 [PATCH i-g-t v2 0/9] Xe: Add tests for PXP Daniele Ceraolo Spurio
2025-01-16 0:19 ` [PATCH i-g-t v2 1/9] drm-uapi/xe: Sync PXP uapi updates Daniele Ceraolo Spurio
2025-01-16 0:19 ` [PATCH i-g-t v2 2/9] tests/intel/xe_vm: Update invalid flag subtest Daniele Ceraolo Spurio
2025-01-16 21:55 ` Teres Alexis, Alan Previn
2025-01-16 0:19 ` [PATCH i-g-t v2 3/9] tests/intel/xe_query: Add test for PXP status query Daniele Ceraolo Spurio
2025-01-16 0:19 ` [PATCH i-g-t v2 4/9] tests/intel/xe_create: Stop treating the extension field as MBZ Daniele Ceraolo Spurio
2025-01-16 22:02 ` Teres Alexis, Alan Previn [this message]
2025-01-16 0:19 ` [PATCH i-g-t v2 5/9] tests/intel/xe_exec_queue_property: Update first invalid property value Daniele Ceraolo Spurio
2025-01-16 22:06 ` Teres Alexis, Alan Previn
2025-01-16 0:19 ` [PATCH i-g-t v2 6/9] tests/intel/xe_pxp: Add PXP object and queue creation tests Daniele Ceraolo Spurio
2025-01-16 22:16 ` Teres Alexis, Alan Previn
2025-01-16 0:19 ` [PATCH i-g-t v2 7/9] tests/intel/xe_pxp: Test PXP submissions Daniele Ceraolo Spurio
2025-01-28 2:44 ` Teres Alexis, Alan Previn
2025-01-16 0:19 ` [PATCH i-g-t v2 8/9] tests/intel/xe_pxp: Termination tests Daniele Ceraolo Spurio
2025-01-28 5:13 ` Teres Alexis, Alan Previn
2025-01-16 0:19 ` [PATCH i-g-t v2 9/9] tests/intel/xe_pxp: Test encrypted FBs Daniele Ceraolo Spurio
2025-01-31 1:47 ` Teres Alexis, Alan Previn
2025-01-16 4:55 ` ✓ Xe.CI.BAT: success for Xe: Add tests for PXP (rev2) Patchwork
2025-01-16 4:56 ` ✓ i915.CI.BAT: " Patchwork
2025-01-16 9:38 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-17 10:03 ` ✗ 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=7626a11d90ed144fce3125421632746059eceb68.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=igt-dev@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