From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: linux-kernel@vger.kernel.org, chrisw@sous-sol.org,
alan@lxorguk.ukuu.org.uk, davej@redhat.com, ak@muc.de
Subject: [PATCH][OPROFILE] x86: Use for_each_possible_cpu to allocate msrs (was [PATCH] x86: fix oprofile double free (was Re: Multiple free during oprofile unload))
Date: Wed, 30 May 2007 23:24:27 -0300 [thread overview]
Message-ID: <20070531022427.GA21633@ghostprotocols.net> (raw)
The fix for the fix needed a fix: allocate_msrs() was using
for_each_online_cpu(), but nmi_setup uses for_each_possible_cpu(), and
in my test machine, a Dell Poweredge 1950 I have 2 dual core Xeons,
which makes for 4 possible cores, but wait, they are HT capable, so...
[acme@mica linux-2.6.21.3.orig]$ dmesg | grep Allowing
SMP: Allowing 8 CPUs, 4 hotplug CPUs
[acme@mica linux-2.6.21.3.orig]$
We have 8 possible CPUs, but only 4 online, b00m. Fix it by making
allocate_msrs agree with nmi_setup, i.e. make both use
for_each_possible_cpu().
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
diff -uNrp linux-2.6.21.3.orig/arch/i386/oprofile/nmi_int.c linux-2.6.21.3.new/arch/i386/oprofile/nmi_int.c
--- linux-2.6.21.3.orig/arch/i386/oprofile/nmi_int.c 2007-05-30 23:08:33.000000000 -0300
+++ linux-2.6.21.3.new/arch/i386/oprofile/nmi_int.c 2007-05-30 23:09:17.000000000 -0300
@@ -154,7 +154,7 @@ static int allocate_msrs(void)
size_t counters_size = sizeof(struct op_msr) * model->num_counters;
int i;
- for_each_online_cpu(i) {
+ for_each_possible_cpu(i) {
cpu_msrs[i].counters = kmalloc(counters_size, GFP_KERNEL);
if (!cpu_msrs[i].counters) {
success = 0;
next reply other threads:[~2007-05-31 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 2:24 Arnaldo Carvalho de Melo [this message]
2007-05-31 6:09 ` [PATCH][OPROFILE] x86: Use for_each_possible_cpu to allocate msrs (was [PATCH] x86: fix oprofile double free (was Re: Multiple free during oprofile unload)) Chris Wright
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=20070531022427.GA21633@ghostprotocols.net \
--to=acme@redhat.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisw@sous-sol.org \
--cc=davej@redhat.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox