mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: oprofile-list@lists.sf.net, robert.richter@amd.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH] [3/3] oprofile: add support for Core i7 and Atom
Date: Mon, 27 Apr 2009 17:44:13 +0200 (CEST)	[thread overview]
Message-ID: <20090427154413.2DE2B1D0232@basil.firstfloor.org> (raw)
In-Reply-To: <20090427544.130860995@firstfloor.org>


The registers are about the same as other Family 6 CPUs 
so we only need to add detection.

I'm not completely happy with calling Nehalem Core i7 because
there will be undoubtedly other Nehalem based CPUs
in the future with different marketing names, but it's
the best we got for now.

Requires updated oprofile userland for the new event files.

If you don't want to update right now you can also use 
oprofile.force_arch_perfmon=1 (added in the next patch) with 0.9.4

Signed-off-by: Andi Kleen <ak@linux.intel.com>

---
 arch/x86/oprofile/nmi_int.c |    7 +++++++
 1 file changed, 7 insertions(+)

Index: linux-2.6.30-rc3-ak/arch/x86/oprofile/nmi_int.c
===================================================================
--- linux-2.6.30-rc3-ak.orig/arch/x86/oprofile/nmi_int.c	2009-04-27 13:25:08.000000000 +0200
+++ linux-2.6.30-rc3-ak/arch/x86/oprofile/nmi_int.c	2009-04-27 15:36:22.000000000 +0200
@@ -417,6 +417,13 @@
 	case 15: case 23:
 		*cpu_type = "i386/core_2";
 		break;
+	case 26:
+		arch_perfmon_setup_counters();
+		*cpu_type = "i386/core_i7";
+		break;
+	case 28:
+		*cpu_type = "i386/atom";
+		break;
 	default:
 		/* Unknown */
 		return 0;

  parent reply	other threads:[~2009-04-27 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 15:44 [PATCH] [1/3] oprofile: re-add force_arch_perfmon option Andi Kleen
2009-04-27 15:44 ` [PATCH] [2/3] oprofile: remove undocumented oprofile.p4force option Andi Kleen
2009-04-27 15:44 ` Andi Kleen [this message]
2009-05-06 12:50 ` [PATCH] [1/3] oprofile: re-add force_arch_perfmon option Robert Richter
2009-05-06 14:48   ` 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=20090427154413.2DE2B1D0232@basil.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sf.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

all inboxes | Powered by JetHome®