From: Oak Zeng <oak.zeng@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Thomas.Hellstrom@linux.intel.com, matthew.brost@intel.com
Subject: [i-g-t 1/4] lib/xe: Fix a comment error
Date: Thu, 13 Feb 2025 10:40:45 -0500 [thread overview]
Message-ID: <20250213154048.273437-1-oak.zeng@intel.com> (raw)
The timeout value of __xe_wait_ufence returns the
remaining time, not elapsed time. Fix it.
Signed-off-by: Oak Zeng <oak.zeng@intel.com>
---
lib/xe/xe_ioctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/xe/xe_ioctl.c b/lib/xe/xe_ioctl.c
index 6d8388918..028102aa2 100644
--- a/lib/xe/xe_ioctl.c
+++ b/lib/xe/xe_ioctl.c
@@ -496,7 +496,7 @@ void xe_exec_wait(int fd, uint32_t exec_queue, uint64_t addr)
*
* Function compares @value with memory pointed by @addr until they are equal.
*
- * Returns (in @timeout), the elapsed time in nanoseconds if user fence was
+ * Returns (in @timeout), the remaining time in nanoseconds if user fence was
* signalled. Returns 0 on success, -errno of ioctl on error.
*/
int __xe_wait_ufence(int fd, uint64_t *addr, uint64_t value,
--
2.26.3
next reply other threads:[~2025-02-13 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 15:40 Oak Zeng [this message]
2025-02-13 15:40 ` [i-g-t 2/4] lib/xe/xe_util: Introduce helper functions for buffer creation and command submission etc Oak Zeng
2025-02-13 15:40 ` [i-g-t 3/4] tests/intel/xe_vm: Exclude invalid_flags tests from LNL and BMG Oak Zeng
2025-02-13 15:40 ` [i-g-t 4/4] tests/intel/xe_exec_fault_mode: Test scratch page under fault mode Oak Zeng
2025-02-13 16:23 ` ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/4] lib/xe: Fix a comment error Patchwork
2025-02-13 16:45 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-13 16:55 ` ✓ i915.CI.BAT: " Patchwork
2025-02-13 23:40 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-14 10:43 ` ✗ Xe.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 22:27 [i-g-t 1/4] " Oak Zeng
2025-02-13 2:19 Oak Zeng
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=20250213154048.273437-1-oak.zeng@intel.com \
--to=oak.zeng@intel.com \
--cc=Thomas.Hellstrom@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.brost@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