From: Chris Wright <chrisw@sous-sol.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
John Levon <levon@movementarian.org>,
linux-kernel@vger.kernel.org, chrisw@sous-sol.org,
alan@lxorguk.ukuu.org.uk, davej@redhat.com, ak@muc.de
Subject: Re: [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:09:38 -0700 [thread overview]
Message-ID: <20070531060938.GK3429@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070531022427.GA21633@ghostprotocols.net>
* Arnaldo Carvalho de Melo (acme@redhat.com) wrote:
> 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>
Acked-by: Chris Wright <chrisw@sous-sol.org>
Thanks Arnaldo. I noticed this earlier, but mistakenly didn't consider it
an issue aside of code needing to be cleaned up and for hotplug (which I
thought was already broken for other reasons). And the Opteron I tested
on has possible == online. I tested this addition on both the AMD box,
as well as an Intel box with possible > online. All looks good.
thanks,
-chris
prev parent reply other threads:[~2007-05-31 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 2:24 [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)) Arnaldo Carvalho de Melo
2007-05-31 6:09 ` Chris Wright [this message]
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=20070531060938.GK3429@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=acme@redhat.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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