From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, rostedt@goodmis.org, Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 4/4] Add trace decoding script to add MSR names to MSR trace
Date: Fri, 10 Oct 2014 14:47:53 -0700 [thread overview]
Message-ID: <1412977673-13500-4-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1412977673-13500-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Add the MSR names from msr-index.h to a trace including read/write_msr
events. This makes the output much easier to read.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
Documentation/trace/postprocess/decode_msr.py | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100755 Documentation/trace/postprocess/decode_msr.py
diff --git a/Documentation/trace/postprocess/decode_msr.py b/Documentation/trace/postprocess/decode_msr.py
new file mode 100755
index 0000000..e3aa832
--- /dev/null
+++ b/Documentation/trace/postprocess/decode_msr.py
@@ -0,0 +1,22 @@
+#!/usr/bin/python
+# add symbolic names to read_msr / write_msr events in trace
+# decode_msr $kernel/arch/x86/include/uapi/asm/msr-index.h < trace
+
+import sys
+import re
+
+msrs = dict()
+
+with open(sys.argv[1], "r") as f:
+ for j in f:
+ m = re.match(r'#define (MSR_\w+)\s+(0x[0-9a-fA-F]+)', j)
+ if m:
+ msrs[int(m.group(2), 16)] = m.group(1)
+
+for j in sys.stdin:
+ m = re.search(r'(read|write)_msr: ([0-9a-f]+)', j)
+ if m and int(m.group(2), 16) in msrs:
+ j = j.replace(" " + m.group(2), " " + msrs[int(m.group(2), 16)])
+ print j,
+
+
--
1.9.3
prev parent reply other threads:[~2014-10-10 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 21:47 [PATCH 1/4] x86: Move msr accesses out of line Andi Kleen
2014-10-10 21:47 ` [PATCH 2/4] x86: Add trace point for MSR accesses Andi Kleen
2014-10-10 21:47 ` [PATCH 3/4] perf, x86: Remove old MSR tracing code Andi Kleen
2014-10-10 21:47 ` Andi Kleen [this message]
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=1412977673-13500-4-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@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
all inboxes | Powered by JetHome®