From: janga.rahul.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com,
janga.rahul.kumar@intel.com
Cc: matthew.d.roper@intel.com, badal.nilawar@intel.com
Subject: [PATCH i-g-t v3 0/3] Add mocs tests
Date: Sat, 4 May 2024 18:34:55 +0530 [thread overview]
Message-ID: <20240504130458.2102132-1-janga.rahul.kumar@intel.com> (raw)
From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
Add below mocs tests:
1. Test to read and dump mocs debugfs entry
2. Test to check mocs values retained over suspend/resume.
3. Test to check mocs values retained over S2/S3/S4 suspend
resume states.
Below patch add mocs debugfs in kernel:
https://patchwork.freedesktop.org/series/131425/
v2: Address review comments. Add S2/S3 tests. (Matt Roper)
v3: Address review comments. (Badal Nilawar)
Janga Rahul Kumar (3):
tests/intel/xe_debugfs: Extend gt test to check mocs entry
tests/intel/xe_pm: Add mocs runtime suspend resume test
tests/intel/xe_pm: Add mocs S2-idle/S3/S4 suspend resume test
tests/intel/xe_debugfs.c | 5 ++++
tests/intel/xe_pm.c | 52 ++++++++++++++++++++++++++++++++++++++++
2 files changed, 57 insertions(+)
--
2.25.1
next reply other threads:[~2024-05-04 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 13:04 janga.rahul.kumar [this message]
2024-05-04 13:04 ` [PATCH i-g-t 1/3] tests/intel/xe_debugfs: Extend gt test to check mocs entry janga.rahul.kumar
2024-05-04 13:04 ` [PATCH i-g-t 2/3] tests/intel/xe_pm: Add mocs runtime suspend resume test janga.rahul.kumar
2024-05-07 9:42 ` Nilawar, Badal
2024-05-04 13:04 ` [PATCH i-g-t 3/3] tests/intel/xe_pm: Add mocs S2-idle/S3/S4 " janga.rahul.kumar
2024-05-07 9:50 ` Nilawar, Badal
2024-05-07 12:42 ` Rodrigo Vivi
2024-05-04 13:42 ` ✓ Fi.CI.BAT: success for Add mocs tests (rev3) Patchwork
2024-05-04 13:45 ` ✓ CI.xeBAT: " Patchwork
2024-05-04 14:43 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-04 14:48 ` ✓ Fi.CI.IGT: success " 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=20240504130458.2102132-1-janga.rahul.kumar@intel.com \
--to=janga.rahul.kumar@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=ramadevi.gandi@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