linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: <linuxppc-dev@ozlabs.org>
Cc: sam.bobroff@au1.ibm.com
Subject: [PATCH 05/10] selftests/powerpc: Count instructions under scheduler pressure
Date: Wed, 23 Jul 2014 17:31:35 +1000	[thread overview]
Message-ID: <1406100700-9702-5-git-send-email-mpe@ellerman.id.au> (raw)
In-Reply-To: <1406100700-9702-1-git-send-email-mpe@ellerman.id.au>

Have a task eat some cpu while we are counting instructions to create
some scheduler pressure. The idea being to try and unearth any bugs we
have in counting that only appear when context switching is happening.

Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
 tools/testing/selftests/powerpc/pmu/Makefile             | 2 +-
 tools/testing/selftests/powerpc/pmu/count_instructions.c | 8 +++++++-
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/powerpc/pmu/Makefile b/tools/testing/selftests/powerpc/pmu/Makefile
index ebc0e7449cd9..8595cfd7e41b 100644
--- a/tools/testing/selftests/powerpc/pmu/Makefile
+++ b/tools/testing/selftests/powerpc/pmu/Makefile
@@ -2,7 +2,7 @@ noarg:
 	$(MAKE) -C ../
 
 PROGS := count_instructions l3_bank_test
-EXTRA_SOURCES := ../harness.c event.c
+EXTRA_SOURCES := ../harness.c event.c lib.c
 
 SUB_TARGETS = ebb
 
diff --git a/tools/testing/selftests/powerpc/pmu/count_instructions.c b/tools/testing/selftests/powerpc/pmu/count_instructions.c
index 312b4f0fd27c..5e241e14f204 100644
--- a/tools/testing/selftests/powerpc/pmu/count_instructions.c
+++ b/tools/testing/selftests/powerpc/pmu/count_instructions.c
@@ -12,6 +12,7 @@
 
 #include "event.h"
 #include "utils.h"
+#include "lib.h"
 
 extern void thirty_two_instruction_loop(u64 loops);
 
@@ -90,7 +91,7 @@ static u64 determine_overhead(struct event *events)
 	return overhead;
 }
 
-static int count_instructions(void)
+static int test_body(void)
 {
 	struct event events[2];
 	u64 overhead;
@@ -129,6 +130,11 @@ static int count_instructions(void)
 	return 0;
 }
 
+static int count_instructions(void)
+{
+	return eat_cpu(test_body);
+}
+
 int main(void)
 {
 	return test_harness(count_instructions, "count_instructions");
-- 
1.9.1

  parent reply	other threads:[~2014-07-23  7:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  7:31 [PATCH 01/10] selftests/powerpc: Don't ignore errors from sub Makefiles Michael Ellerman
2014-07-23  7:31 ` [PATCH 02/10] selftests/powerpc: Fix parse_proc_maps() Michael Ellerman
2014-07-23  7:31 ` [PATCH 03/10] selftests/powerpc: Move core_busy_loop() into asm Michael Ellerman
2014-07-23  7:31 ` [PATCH 04/10] selftests/powerpc: Add test of L3 bank handling Michael Ellerman
2014-07-23  7:31 ` Michael Ellerman [this message]
2014-07-23  7:31 ` [PATCH 06/10] selftests/powerpc: Count more instructions & use decimal Michael Ellerman
2014-07-23  7:31 ` [PATCH 07/10] selftests/powerpc: Dump MMCR2 as part of the EBB HW state Michael Ellerman
2014-07-23  7:31 ` [PATCH 08/10] selftests/powerpc: Add cycles test with MMCR2 handling Michael Ellerman
2014-07-23  7:31 ` [PATCH 09/10] selftests/powerpc: Add a routine for retrieving an AUXV entry Michael Ellerman
2014-07-23  7:31 ` [PATCH 10/10] selftests/powerpc: Add test of per-event excludes Michael Ellerman

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=1406100700-9702-5-git-send-email-mpe@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sam.bobroff@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).