From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Thomas Richter <tmricht@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 5/7] perf data: Update documentation section on cpu topology
Date: Thu, 31 May 2018 07:32:18 -0300 [thread overview]
Message-ID: <20180531103220.24684-6-acme@kernel.org> (raw)
In-Reply-To: <20180531103220.24684-1-acme@kernel.org>
From: Thomas Richter <tmricht@linux.ibm.com>
Add an explanation of each cpu's core and socket identifier to the
perf.data file format documentation.
Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Link: http://lkml.kernel.org/r/20180528074433.16652-1-tmricht@linux.ibm.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf.data-file-format.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/perf/Documentation/perf.data-file-format.txt b/tools/perf/Documentation/perf.data-file-format.txt
index d00f0d51cab8..c57904a526ce 100644
--- a/tools/perf/Documentation/perf.data-file-format.txt
+++ b/tools/perf/Documentation/perf.data-file-format.txt
@@ -153,10 +153,18 @@ struct {
HEADER_CPU_TOPOLOGY = 13,
String lists defining the core and CPU threads topology.
+The string lists are followed by a variable length array
+which contains core_id and socket_id of each cpu.
+The number of entries can be determined by the size of the
+section minus the sizes of both string lists.
struct {
struct perf_header_string_list cores; /* Variable length */
struct perf_header_string_list threads; /* Variable length */
+ struct {
+ uint32_t core_id;
+ uint32_t socket_id;
+ } cpus[nr]; /* Variable length records */
};
Example:
--
2.14.3
next prev parent reply other threads:[~2018-05-31 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 10:32 [GIT PULL 0/7] perf/urgent fixes Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` [PATCH 1/7] perf parse-events: Handle uncore event aliases in small groups properly Arnaldo Carvalho de Melo
2018-05-31 10:32 ` [PATCH 2/7] perf test: "Session topology" dumps core on s390 Arnaldo Carvalho de Melo
2018-05-31 10:32 ` [PATCH 3/7] perf bpf: Fix NULL return handling in bpf__prepare_load() Arnaldo Carvalho de Melo
2018-05-31 10:32 ` [PATCH 4/7] perf cs-etm: Fix indexing for decoder packet queue Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo [this message]
2018-05-31 10:32 ` [PATCH 6/7] perf script python: Add addr into perf sample dict Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` [PATCH 7/7] perf tools: Fix perf.data format description of NRCPUS header Arnaldo Carvalho de Melo
2018-05-31 10:40 ` [GIT PULL 0/7] perf/urgent fixes Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
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=20180531103220.24684-6-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.ibm.com \
--cc=williams@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.