From: Andi Kleen <andi@firstfloor.org>
To: oprofile-list@lists.sf.net, robert.richter@amd.com,
linux-kernel@vger.kernel.org
Subject: [PATCH] [2/3] oprofile: remove undocumented oprofile.p4force option
Date: Mon, 27 Apr 2009 17:44:12 +0200 (CEST) [thread overview]
Message-ID: <20090427154412.290C61D024B@basil.firstfloor.org> (raw)
In-Reply-To: <20090427544.130860995@firstfloor.org>
There are no new P4s and the oprofile code knows about all existing
ones, so we don't really need the p4force option anymore.
Remove it.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
arch/x86/oprofile/nmi_int.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
Index: linux-2.6.28-test/arch/x86/oprofile/nmi_int.c
===================================================================
--- linux-2.6.28-test.orig/arch/x86/oprofile/nmi_int.c 2009-01-03 00:57:30.000000000 +0100
+++ linux-2.6.28-test/arch/x86/oprofile/nmi_int.c 2009-01-03 00:58:25.000000000 +0100
@@ -356,14 +356,11 @@
#define exit_sysfs() do { } while (0)
#endif /* CONFIG_PM */
-static int p4force;
-module_param(p4force, int, 0);
-
static int __init p4_init(char **cpu_type)
{
__u8 cpu_model = boot_cpu_data.x86_model;
- if (!p4force && (cpu_model > 6 || cpu_model == 5))
+ if (cpu_model > 6 || cpu_model == 5)
return 0;
#ifndef CONFIG_SMP
next prev parent reply other threads:[~2009-04-27 15:44 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 ` Andi Kleen [this message]
2009-04-27 15:44 ` [PATCH] [3/3] oprofile: add support for Core i7 and Atom Andi Kleen
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=20090427154412.290C61D024B@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