From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Mika Kuoppala" <mika.kuoppala@linux.intel.com>,
"Dominik Grzegorzek" <dominik.grzegorzek@intel.com>,
"Christoph Manszewski" <christoph.manszewski@intel.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Dominik Karol Piątkowski" <dominik.karol.piatkowski@intel.com>
Subject: [PATCH i-g-t] tests/xe_eudebug: add basic-vm-access-parameters-userptr
Date: Thu, 19 Dec 2024 15:39:26 +0200 [thread overview]
Message-ID: <20241219133926.2334476-1-mika.kuoppala@linux.intel.com> (raw)
There is an easy way to also use the access-parameters test
to be based on userptr backing storage. Make it so.
Cc: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
Cc: Christoph Manszewski <christoph.manszewski@intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Dominik Karol Piątkowski <dominik.karol.piatkowski@intel.com>
Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
tests/intel/xe_eudebug.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/tests/intel/xe_eudebug.c b/tests/intel/xe_eudebug.c
index d9281f78f..dc8e587b7 100644
--- a/tests/intel/xe_eudebug.c
+++ b/tests/intel/xe_eudebug.c
@@ -1773,7 +1773,13 @@ static void vm_trigger_access_parameters(struct xe_eudebug_debugger *d,
/**
* SUBTEST: basic-vm-access-parameters
* Description:
- * Check negative scenarios of VM_OPEN ioctl and pread/pwrite usage.
+ * Check negative scenarios of VM_OPEN ioctl and pread/pwrite usage
+ * with bo backing storage.
+ *
+ * SUBTEST: basic-vm-access-parameters-userptr
+ * Description:
+ * Check negative scenarios of VM_OPEN ioctl and pread/pwrite usage
+ * with userptr backing storage.
*/
static void test_vm_access_parameters(int fd, unsigned int flags, int num_clients)
{
@@ -2830,6 +2836,9 @@ igt_main
igt_subtest("basic-vm-access-parameters")
test_vm_access_parameters(fd, 0, 1);
+ igt_subtest("basic-vm-access-parameters-userptr")
+ test_vm_access_parameters(fd, VM_BIND_OP_MAP_USERPTR, 1);
+
igt_subtest("multiple-sessions")
test_basic_sessions(fd, CREATE_VMS | CREATE_EXEC_QUEUES, 4, true);
--
2.43.0
next reply other threads:[~2024-12-19 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 13:39 Mika Kuoppala [this message]
2024-12-19 13:47 ` [PATCH i-g-t] tests/xe_eudebug: add basic-vm-access-parameters-userptr Piatkowski, Dominik Karol
2024-12-19 16:06 ` ✗ GitLab.Pipeline: warning for " Patchwork
2024-12-19 16:28 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-19 16:49 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-20 11:49 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-20 15:17 ` ✗ 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=20241219133926.2334476-1-mika.kuoppala@linux.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=christoph.manszewski@intel.com \
--cc=dominik.grzegorzek@intel.com \
--cc=dominik.karol.piatkowski@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