linux-kernel - Adding MSR trace points, new edition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1445458478-16716-1-git-send-email-andi@firstfloor.org>
Date:	Wed, 21 Oct 2015 13:14:34 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	x86@...nel.org
Cc:	rostedt@...dmis.org, peterz@...radead.org,
	linux-kernel@...r.kernel.org
Subject: Adding MSR trace points, new edition

[v2: Move trace header into architecture specific include]

For debugging perf it's very useful to trace CPU MSR read / writes.
perf has a hackish way to do it, but it does not support reads,
requires hacking a header file, and cannot be used with triggers.

MSR accesses are inlined, which makes it difficult to directly
add trace points to them.

I posted a patch some time ago that moved them out of line
to make it possible to trace them.

Steven proposed a different approach of open coding the trace point
static key access. This patchkit implements the different approach.

To avoid include loops, it required some changes in the trace point
and in the x86 headers. These can be considered cleanups in thri own.
This is implemented in the first two patches.

Then the later patch adds the actual trace points, and a pretty
printing script for them, and then finally removes the old hackish
perf MSR tracing.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/