From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 1/3] tests/intel/xe_vm: Update first invalid flag number
Date: Thu, 30 Jan 2025 14:36:07 -0800 [thread overview]
Message-ID: <85zfj8dj54.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250130221457.1092670-2-daniele.ceraolospurio@intel.com>
On Thu, 30 Jan 2025 14:14:55 -0800, Daniele Ceraolo Spurio wrote:
>
> PXP introduces a new valid flag [1], so to avoid the invalid_flag test
> failing we need to prepare by shifting the first invalid bit left by one.
> The testing of the valid flag will be added later once the PXP kernel side
> is merged.
>
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> [1] https://patchwork.freedesktop.org/patch/634550/
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@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 6ee3f4634..0730dd3d3 100644
> --- a/tests/intel/xe_vm.c
> +++ b/tests/intel/xe_vm.c
> @@ -2234,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);
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-01-30 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 22:14 [PATCH i-g-t 0/3] Prepare for new PXP UAPI flags Daniele Ceraolo Spurio
2025-01-30 22:14 ` [PATCH i-g-t 1/3] tests/intel/xe_vm: Update first invalid flag number Daniele Ceraolo Spurio
2025-01-30 22:36 ` Dixit, Ashutosh [this message]
2025-01-30 22:14 ` [PATCH i-g-t 2/3] tests/intel/xe_create: Stop treating the extension field as MBZ Daniele Ceraolo Spurio
2025-01-31 12:59 ` Kamil Konieczny
2025-01-31 17:09 ` Daniele Ceraolo Spurio
2025-01-31 17:28 ` Kamil Konieczny
2025-01-30 22:14 ` [PATCH i-g-t 3/3] tests/intel/xe_exec_queue_property: Update first invalid property value Daniele Ceraolo Spurio
2025-01-30 23:07 ` ✓ Xe.CI.BAT: success for Prepare for new PXP UAPI flags Patchwork
2025-01-30 23:20 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-31 3:48 ` ✗ Xe.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=85zfj8dj54.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@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