[Intel-gfx] [igt-gpu-tools] Fixing the latency of hrtimer
Sowmya Kaparthi
sowmyax.kaparthi at intel.com
Wed Aug 26 18:36:35 UTC 2020
The blocking/polling parameterized tests were introduced to test
different hrtimer configurations.These tests check how many times the
process wakes up to read the reports with different hrtimer values (=
duration of test / hrtimer value). A user is more likely to choose a
larger hrtimer value than the default 5ms to avoid wake up too frequently.
Signed-off-by: Sowmya Kaparthi <sowmyax.kaparthi at intel.com>
---
tests/i915/perf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/i915/perf.c b/tests/i915/perf.c
index a894fd38..5fd1193f 100644
--- a/tests/i915/perf.c
+++ b/tests/i915/perf.c
@@ -4995,7 +4995,7 @@ igt_main
40 * 1000 * 1000 /* default 40ms hrtimer */);
test_blocking(500 * 1000 /* 500us oa period */,
true /* set_kernel_hrtimer */,
- 2 * 1000 * 1000 /* default 2ms hrtimer */);
+ 10 * 1000 * 1000 /* default 10ms hrtimer */);
}
igt_describe("Test polled read with default hrtimer frequency");
@@ -5014,7 +5014,7 @@ igt_main
40 * 1000 * 1000 /* default 40ms hrtimer */);
test_polling(500 * 1000 /* 500us oa period */,
true /* set_kernel_hrtimer */,
- 2 * 1000 * 1000 /* default 2ms hrtimer */);
+ 10 * 1000 * 1000 /* default 10ms hrtimer */);
}
igt_describe("Test polled read with buffer size smaller than available data");
--
2.25.1
More information about the Intel-gfx
mailing list