On 22/05/2018 12:00, Chris Wilson wrote:
Normally we use a hog per CPU to ensure that the system is fully
loaded to see how much latency we cause. For simple sanitychecking, allow
ourselves to limit it to just one CPU hog.
Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
---
benchmarks/gem_syslatency.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/benchmarks/gem_syslatency.c b/benchmarks/gem_syslatency.c
index 9160e2199..d1056773a 100644
--- a/benchmarks/gem_syslatency.c
+++ b/benchmarks/gem_syslatency.c
@@ -311,8 +311,11 @@ int main(int argc, char **argv)
bool interrupts = false;
int n, c;
- while ((c = getopt(argc, argv, "t:f:bmni")) != -1) {
+ while ((c = getopt(argc, argv, "t:f:bmni1")) != -1) {
switch (c) {
+ case '1':
+ ncpus = 1;
+ break;
case 'n': /* dry run, measure baseline system latency */
enable_gem_sysbusy = 0;
break;
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
