From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>, Matthew Auld <matthew.auld@intel.com>
Subject: [PATCH] drm/xe/tests: Use uninterruptible VM lock
Date: Tue, 21 May 2024 12:27:15 +0200 [thread overview]
Message-ID: <20240521102715.22700-1-nirmoy.das@intel.com> (raw)
Interruptible lock can return error and needed a return value
check. This test should finish quick enough so use a uninterruptible
lock instead.
Cc: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
drivers/gpu/drm/xe/tests/xe_migrate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/tests/xe_migrate.c b/drivers/gpu/drm/xe/tests/xe_migrate.c
index b6e7f80c3774..962f6438e219 100644
--- a/drivers/gpu/drm/xe/tests/xe_migrate.c
+++ b/drivers/gpu/drm/xe/tests/xe_migrate.c
@@ -344,7 +344,7 @@ static int migrate_test_run_device(struct xe_device *xe)
struct xe_migrate *m = tile->migrate;
kunit_info(test, "Testing tile id %d.\n", id);
- xe_vm_lock(m->q->vm, true);
+ xe_vm_lock(m->q->vm, false);
xe_migrate_sanity_test(m, test);
xe_vm_unlock(m->q->vm);
}
--
2.42.0
next reply other threads:[~2024-05-21 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:27 Nirmoy Das [this message]
2024-05-21 10:45 ` [PATCH] drm/xe/tests: Use uninterruptible VM lock Matthew Auld
2024-05-21 11:28 ` ✓ CI.Patch_applied: success for " Patchwork
2024-05-21 11:29 ` ✓ CI.checkpatch: " Patchwork
2024-05-21 11:30 ` ✓ CI.KUnit: " Patchwork
2024-05-21 11:41 ` ✓ CI.Build: " Patchwork
2024-05-21 11:44 ` ✓ CI.Hooks: " Patchwork
2024-05-21 11:45 ` ✓ CI.checksparse: " Patchwork
2024-05-21 12:22 ` ✓ CI.BAT: " Patchwork
2024-05-21 15:34 ` ✗ CI.FULL: failure " Patchwork
2024-05-21 20:15 ` Nirmoy Das
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=20240521102715.22700-1-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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