public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kan Liang <kan.liang@intel.com>
To: acme@kernel.org, jolsa@kernel.org
Cc: ak@linux.intel.com, linux-kernel@vger.kernel.org,
	Kan Liang <kan.liang@intel.com>
Subject: [PATCH V4 3/3] perf,test: test cpu topology
Date: Tue,  1 Sep 2015 09:58:13 -0400	[thread overview]
Message-ID: <1441115893-22006-3-git-send-email-kan.liang@intel.com> (raw)
In-Reply-To: <1441115893-22006-1-git-send-email-kan.liang@intel.com>

From: Jiri Olsa <jolsa@kernel.org>

This patch test cpu core_id and socket_id which are stored in perf_env.

Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Signed-off-by: Kan Liang <kan.liang@intel.com>
---

Changes since jirka's original version
 - Use pr_debug to replace fprintf
 - Add date_size to avoid warning
 - Introduce cpu_map, and compare core_id and socket_id
   between cpu_map and perf_env

Changes since V2:
 - unlink(path)

 tools/perf/tests/Build          | 1 +
 tools/perf/tests/builtin-test.c | 4 ++++
 tools/perf/tests/tests.h        | 1 +
 3 files changed, 6 insertions(+)

diff --git a/tools/perf/tests/Build b/tools/perf/tests/Build
index c1518bd..208bbdf 100644
--- a/tools/perf/tests/Build
+++ b/tools/perf/tests/Build
@@ -33,6 +33,7 @@ perf-y += parse-no-sample-id-all.o
 perf-y += kmod-path.o
 perf-y += thread-map.o
 perf-y += llvm.o
+perf-y += topology.o
 
 perf-$(CONFIG_X86) += perf-time-to-tsc.o
 
diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
index 136cd93..6650f26 100644
--- a/tools/perf/tests/builtin-test.c
+++ b/tools/perf/tests/builtin-test.c
@@ -179,6 +179,10 @@ static struct test {
 		.func = test__llvm,
 	},
 	{
+		.desc = "Test topology in session",
+		.func = test_session_topology,
+	},
+	{
 		.func = NULL,
 	},
 };
diff --git a/tools/perf/tests/tests.h b/tools/perf/tests/tests.h
index bf113a2..95654d7 100644
--- a/tools/perf/tests/tests.h
+++ b/tools/perf/tests/tests.h
@@ -63,6 +63,7 @@ int test__fdarray__add(void);
 int test__kmod_path__parse(void);
 int test__thread_map(void);
 int test__llvm(void);
+int test_session_topology(void);
 
 #if defined(__x86_64__) || defined(__i386__) || defined(__arm__) || defined(__aarch64__)
 #ifdef HAVE_DWARF_UNWIND_SUPPORT
-- 
1.8.3.1


  parent reply	other threads:[~2015-09-01 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:58 [PATCH V4 1/3] perf,tools: Separated functions to get core_id and socket_id Kan Liang
2015-09-01 13:58 ` [PATCH V4 2/3] perf,tools: store cpu socket_id and core_id in perf.date Kan Liang
2015-09-01 22:24   ` Arnaldo Carvalho de Melo
2015-09-08 14:32   ` [tip:perf/core] perf tools: Store the cpu socket and core ids in the perf.data header tip-bot for Kan Liang
2015-09-01 13:58 ` Kan Liang [this message]
2015-09-01 22:29   ` [PATCH V4 3/3] perf,test: test cpu topology Arnaldo Carvalho de Melo
2015-09-01 23:25     ` Liang, Kan
2015-09-02  6:03       ` Jiri Olsa
2015-09-08 14:31 ` [tip:perf/core] perf cpumap: Factor out functions to get core_id and socket_id tip-bot for Kan Liang

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=1441115893-22006-3-git-send-email-kan.liang@intel.com \
    --to=kan.liang@intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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