mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Cc: robert.richter@amd.com, oprofile-list@lists.sourceforge.net
Subject: oprofile: Implement Intel architectural perfmon
Date: Wed, 20 Aug 2008 18:40:29 +0200	[thread overview]
Message-ID: <1219250433-25516-1-git-send-email-andi@firstfloor.org> (raw)


This patchkit implements architectural perfmon support in oprofile.
This allows to do generic profiling of a few standard events in all 
newer Intel CPUs, including Atom and Nehalem. The CPU describes
its event in CPUID so they can be used without knowing anything
about the CPU.

The code requires some changes to the oprofile userland, which
I am posting separately to the oprofile list.

-Andi

             reply	other threads:[~2008-08-20 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 16:40 Andi Kleen [this message]
2008-08-20 16:40 ` [PATCH] oprofile: drop const in num counters field Andi Kleen
2008-08-20 16:40   ` [PATCH] oprofile: Implement Intel architectural perfmon support Andi Kleen
2008-08-20 16:40     ` [PATCH] oprofile: Don't report Nehalem as core_2 Andi Kleen
2008-08-20 16:40       ` [PATCH] oprofile: document undocumented oprofile.p4force argument Andi Kleen
2008-09-25 20:10         ` Robert Richter
2008-09-25 20:05       ` [PATCH] oprofile: Don't report Nehalem as core_2 Robert Richter
2008-09-25 20:00     ` [PATCH] oprofile: Implement Intel architectural perfmon support Robert Richter
2008-09-26  0:44       ` Andi Kleen
2008-09-26  3:23         ` Robert Richter
2008-09-26 23:09           ` Andi Kleen
2008-09-28  7:33             ` Robert Richter
2008-09-25 19:32 ` oprofile: Implement Intel architectural perfmon Robert Richter

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=1219250433-25516-1-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=robert.richter@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome