From c4f61ff9e18594b720f983d1a9e9f85a4bcc4f7e Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Wed, 16 May 2018 17:08:03 +0100 Subject: benchmarks/gem_syslatency: Allow limiting to just 1 CPU hog 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 Reviewed-by: Tvrtko Ursulin --- benchmarks/gem_syslatency.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'benchmarks') diff --git a/benchmarks/gem_syslatency.c b/benchmarks/gem_syslatency.c index 62704264..6d520bfe 100644 --- a/benchmarks/gem_syslatency.c +++ b/benchmarks/gem_syslatency.c @@ -316,8 +316,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; -- cgit v1.2.3