From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jonathan.cavitt@intel.com, saurabhg.gupta@intel.com,
alex.zuo@intel.com, kamil.konieczny@linux.intel.com,
vinay.belgaumkar@intel.com
Subject: [PATCH v4 2/2] tests/intel/xe_sysfs_timeslice_duration: Restore preempt timeout
Date: Tue, 5 Nov 2024 20:11:43 +0000 [thread overview]
Message-ID: <20241105201143.159491-3-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20241105201143.159491-1-jonathan.cavitt@intel.com>
The subtests of sysfs_timeslice_duration modify the preempt_timeout_us
and timeslice_duration_us values. However, while the test does restore
the timeslice_duration_us value at the end of execution, it does not do
the same for preempt_timeout_us. Because the value is not properly
restored, future tests can end up using the unexpected preempt timeout
value and thus have unexpected behavior.
Save and restore the preempt_timeout_us value during the test.
This fix does not apply to xe_sysfs_preempt_timeout because only the
preempt_timeout_us is modified during those tests, and the value is
correcty restored before the tests end.
v2: Also restore preempt_timeout_us on test failure (Kamil)
v3: Abort on restore failure (Kamil)
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2976
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
CC: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
CC: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
tests/intel/xe_sysfs_timeslice_duration.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/tests/intel/xe_sysfs_timeslice_duration.c b/tests/intel/xe_sysfs_timeslice_duration.c
index dfcdd7335f..4669272719 100644
--- a/tests/intel/xe_sysfs_timeslice_duration.c
+++ b/tests/intel/xe_sysfs_timeslice_duration.c
@@ -115,10 +115,11 @@ static uint64_t __test_timeout(int fd, int engine, unsigned int timeout, uint16_
static void test_timeout(int fd, int engine, const char **property, uint16_t class, int gt)
{
uint64_t delays[] = { 1000, 50000, 100000, 500000 };
- unsigned int saved;
+ unsigned int saved, old_pt;
uint64_t elapsed;
uint64_t epsilon;
+ igt_assert(igt_sysfs_scanf(engine, "preempt_timeout_us", "%u", &old_pt) == 1);
igt_require(igt_sysfs_printf(engine, "preempt_timeout_us", "%u", 1) == 1);
igt_assert(igt_sysfs_scanf(engine, property[0], "%u", &saved) == 1);
igt_debug("Initial %s:%u\n", property[0], saved);
@@ -140,6 +141,9 @@ static void test_timeout(int fd, int engine, const char **property, uint16_t cla
}
set_timeslice_duration(engine, saved);
+ igt_assert_lte(0, igt_sysfs_printf(engine, "preempt_timeout_us", "%u", old_pt));
+ igt_sysfs_scanf(engine, "preempt_timeout_us", "%u", &saved);
+ igt_assert_eq(saved, old_pt);
}
#define MAX_GTS 8
@@ -159,7 +163,7 @@ igt_main
int gt_count = 0;
int fd = -1, sys_fd, gt;
int engines_fd[MAX_GTS], gt_fd[MAX_GTS];
- unsigned int tds[MAX_GTS];
+ unsigned int tds[MAX_GTS], pts[MAX_GTS];
igt_fixture {
fd = drm_open_driver(DRIVER_XE);
@@ -178,6 +182,9 @@ igt_main
igt_require(igt_sysfs_scanf(engines_fd[gt_count],
"timeslice_duration_us",
"%u", &tds[gt_count]) == 1);
+ igt_require(igt_sysfs_scanf(engines_fd[gt_count],
+ "preempt_timeout_us",
+ "%u", &pts[gt_count]) == 1);
gt_count++;
}
}
@@ -199,6 +206,12 @@ igt_main
for (int i = gt_count - 1; i >= 0; i--) {
unsigned int store = UINT_MAX;
+ igt_assert_lte(0, igt_sysfs_printf(engines_fd[i], "preempt_timeout_us",
+ "%u", pts[i]));
+ igt_sysfs_scanf(engines_fd[i], "preempt_timeout_us", "%u", &store);
+ igt_abort_on_f(store != pts[i], "preempt_timeout_us not restored!\n");
+
+ store = UINT_MAX;
igt_assert_lte(0, igt_sysfs_printf(engines_fd[i], "timeslice_duration_us",
"%u", tds[i]));
igt_sysfs_scanf(engines_fd[i], "timeslice_duration_us", "%u", &store);
--
2.43.0
next prev parent reply other threads:[~2024-11-05 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 20:11 [PATCH v4 0/2] test/intel/xe_sysfs: Restore sysfs params correctly Jonathan Cavitt
2024-11-05 20:11 ` [PATCH v4 1/2] tests/intel/xe_sysfs*: Restore values on test failure Jonathan Cavitt
2024-11-07 18:03 ` Kamil Konieczny
2024-11-07 22:52 ` Cavitt, Jonathan
2024-11-05 20:11 ` Jonathan Cavitt [this message]
2024-11-05 21:20 ` ✓ CI.xeBAT: success for test/intel/xe_sysfs: Restore sysfs params correctly (rev3) Patchwork
2024-11-05 21:37 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-06 12:57 ` Kamil Konieczny
2024-11-07 0:29 ` ✗ CI.xeFULL: " 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=20241105201143.159491-3-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=vinay.belgaumkar@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