From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] oprofile for 2.5.39
Date: Sun, 29 Sep 2002 04:27:56 +0100 [thread overview]
Message-ID: <20020929032756.GA68826@compsoc.man.ac.uk> (raw)
In-Reply-To: <20020929050807.A17869@wotan.suse.de>
On Sun, Sep 29, 2002 at 05:08:07AM +0200, Andi Kleen wrote:
> I think you can easily do that by keeping state per cpu in the
> NMI handler.
You're quite right, it's simpler as well.
I had a distinct memory of not doing this because it wouldn't work
originally, but I forget what the reasoning was.
> smp_processor_id - per cpu data doesn't work from modules]
yes, which was why I don't use it already.
[Are there any advantages to per_cpu stuff over hand-coding, other
than readability ??]
thanks
john
--
"When your name is Winner, that's it. You don't need a nickname."
- Loser Lane
next prev parent reply other threads:[~2002-09-29 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020929014440.GA66796@compsoc.man.ac.uk.suse.lists.linux.kernel>
2002-09-29 2:29 ` [PATCH][RFC] oprofile for 2.5.39 Andi Kleen
2002-09-29 2:52 ` John Levon
2002-09-29 3:08 ` Andi Kleen
2002-09-29 3:14 ` Andi Kleen
2002-09-29 3:27 ` John Levon [this message]
2002-09-29 4:11 ` Anton Blanchard
2002-09-29 3:47 ` Andrew Morton
2002-09-29 3:53 ` John Levon
2002-09-29 1:44 John Levon
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=20020929032756.GA68826@compsoc.man.ac.uk \
--to=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