All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org
Cc: rostedt@goodmis.org, peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Adding MSR trace points, new edition
Date: Wed, 21 Oct 2015 13:14:34 -0700	[thread overview]
Message-ID: <1445458478-16716-1-git-send-email-andi@firstfloor.org> (raw)

[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.



             reply	other threads:[~2015-10-21 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 20:14 Andi Kleen [this message]
2015-10-21 20:14 ` [PATCH 1/4] x86: Don't include asm/processor.h into asm/atomic.h Andi Kleen
2015-10-21 20:14 ` [PATCH 2/4] tracepoints: Move struct tracepoint to new tracepoint-defs.h header Andi Kleen
2015-10-21 20:14 ` [PATCH 3/4] x86: Add trace point for MSR accesses Andi Kleen
2015-10-21 20:14 ` [PATCH 4/4] perf, x86: Remove old MSR perf tracing code Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2015-10-20 18:40 Adding MSR trace points, new edition Andi Kleen

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=1445458478-16716-1-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 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.