From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/7] tests/intel/xe_vm: Update invalid flag subtest
Date: Wed, 11 Dec 2024 16:24:31 -0800 [thread overview]
Message-ID: <16394f40-9549-48f7-aefd-c3b3f316ab67@intel.com> (raw)
In-Reply-To: <20241212001829.2082490-3-daniele.ceraolospurio@intel.com>
On 12/11/2024 4:18 PM, Daniele Ceraolo Spurio wrote:
> PXP introduced a new valid flag, so we need to add it to the test and
> shift the first invalid bit left by one.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> ---
> tests/intel/xe_vm.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_vm.c b/tests/intel/xe_vm.c
> index e78ddd0e5..741dc0c7a 100644
> --- a/tests/intel/xe_vm.c
> +++ b/tests/intel/xe_vm.c
> @@ -2216,6 +2216,11 @@ static void bind_flag_invalid(int fd)
> igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
> syncobj_reset(fd, &sync[0].handle, 1);
>
> + bind.bind.flags = DRM_XE_VM_BIND_FLAG_CHECK_PXP;
> + igt_ioctl(fd, DRM_IOCTL_XE_VM_BIND, &bind);
> + igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
> + syncobj_reset(fd, &sync[0].handle, 1);
Right after sending the patches I realized I forgot to squash a fix to
only perform this ioctl if the PXP interface is supported. Will wait a
bit for comments on other patches before re-spinning this one.
Daniele
> +
> bind.bind.flags = DRM_XE_VM_BIND_FLAG_NULL;
> bind.bind.obj = 0;
> igt_ioctl(fd, DRM_IOCTL_XE_VM_BIND, &bind);
> @@ -2229,7 +2234,7 @@ static void bind_flag_invalid(int fd)
> syncobj_reset(fd, &sync[0].handle, 1);
>
> /* Using invalid flags should not work */
> - bind.bind.flags = 1 << 4;
> + bind.bind.flags = 1 << 5;
> igt_ioctl(fd, DRM_IOCTL_XE_VM_BIND, &bind);
> do_ioctl_err(fd, DRM_IOCTL_XE_VM_BIND, &bind, EINVAL);
>
next prev parent reply other threads:[~2024-12-12 0:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 0:18 [PATCH i-g-t 0/7] Xe: Add tests for PXP Daniele Ceraolo Spurio
2024-12-12 0:18 ` [PATCH i-g-t 1/7] drm-uapi/xe: Sync PXP uapi updates Daniele Ceraolo Spurio
2025-01-15 2:25 ` Teres Alexis, Alan Previn
2025-01-15 23:26 ` Daniele Ceraolo Spurio
2024-12-12 0:18 ` [PATCH i-g-t 2/7] tests/intel/xe_vm: Update invalid flag subtest Daniele Ceraolo Spurio
2024-12-12 0:24 ` Daniele Ceraolo Spurio [this message]
2025-01-15 5:09 ` Teres Alexis, Alan Previn
2024-12-12 0:18 ` [PATCH i-g-t 3/7] tests/intel/xe_query: Add test for PXP status query Daniele Ceraolo Spurio
2025-01-15 5:38 ` Teres Alexis, Alan Previn
2024-12-12 0:18 ` [PATCH i-g-t 4/7] tests/intel/xe_pxp: Add PXP object and queue creation tests Daniele Ceraolo Spurio
2025-01-15 6:17 ` Teres Alexis, Alan Previn
2024-12-12 0:18 ` [PATCH i-g-t 5/7] tests/intel/xe_pxp: Test PXP submissions Daniele Ceraolo Spurio
2024-12-12 0:18 ` [PATCH i-g-t 6/7] tests/intel/xe_pxp: Termination tests Daniele Ceraolo Spurio
2024-12-12 0:18 ` [PATCH i-g-t 7/7] tests/intel/xe_pxp: Test encrypted FBs Daniele Ceraolo Spurio
2024-12-12 1:11 ` ✗ i915.CI.BAT: failure for Xe: Add tests for PXP Patchwork
2024-12-12 2:30 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-12 8:04 ` ✗ Xe.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=16394f40-9549-48f7-aefd-c3b3f316ab67@intel.com \
--to=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