From: Pravalika Gurram <pravalika.gurram@intel.com>
To: lucas.demarchi@intel.com, igt-dev@lists.freedesktop.org
Cc: Pravalika Gurram <pravalika.gurram@intel.com>
Subject: [PATCH 0/2] tests/xe_spin_batch: Add spin-timestamp-check
Date: Wed, 13 Nov 2024 23:22:05 +0530 [thread overview]
Message-ID: <20241113175207.399101-1-pravalika.gurram@intel.com> (raw)
move the spinner related functions to lib
check the ctx_timestamp register post gt reset for each engine.
Pravalika Gurram (2):
lib/xe/xe_spin: move the spinner related functions to lib
tests/xe_spin_batch: Add spin-timestamp-check
lib/xe/xe_spin.c | 116 +++++++++++++++++++++
lib/xe/xe_spin.h | 40 ++++++--
tests/intel/xe_drm_fdinfo.c | 200 +++++++-----------------------------
tests/intel/xe_spin_batch.c | 121 ++++++++++++++++++++++
4 files changed, 304 insertions(+), 173 deletions(-)
--
2.34.1
next reply other threads:[~2024-11-13 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 17:52 Pravalika Gurram [this message]
2024-11-13 17:52 ` [PATCH 1/2] lib/xe/xe_spin: move the spinner related functions to lib Pravalika Gurram
2024-11-28 8:24 ` Peter Senna Tschudin
2024-12-04 9:09 ` Zbigniew Kempczyński
2024-11-13 17:52 ` [PATCH 2/2] tests/xe_spin_batch: Add spin-timestamp-check Pravalika Gurram
2024-11-28 8:26 ` Peter Senna Tschudin
2024-11-13 20:07 ` ✓ Fi.CI.BAT: success for tests/xe_spin_batch: Add spin-timestamp-check (rev4) Patchwork
2024-11-13 20:08 ` ✓ CI.xeBAT: " Patchwork
2024-11-13 20:18 ` ✗ GitLab.Pipeline: warning " Patchwork
2024-11-13 23:33 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-14 6:49 ` ✗ CI.xeFULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 7:44 [PATCH 0/2] tests/xe_spin_batch: Add spin-timestamp-check Pravalika Gurram
2024-11-07 14:33 Pravalika Gurram
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=20241113175207.399101-1-pravalika.gurram@intel.com \
--to=pravalika.gurram@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@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