From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com, drepper@redhat.com, oprofile-list@lists.sf.net
Subject: [PATCH] oprofile for 2.5.42
Date: Sun, 13 Oct 2002 20:38:38 +0100 [thread overview]
Message-ID: <20021013193838.GA95824@compsoc.man.ac.uk> (raw)
http://oprofile.sourceforge.net/oprofile-2.5.html
as usual. This release has two significant changes :
o We got the task release stuff horribly wrong for CLONE_DETACHED tasks
as used by nptl, leading to instant oopsen. I think I have fixed this.
One drawback is that the do_exit()-related code is now an oprofile blind
spot, but I can't see a better solution
o Use _raw forms for the spinlock we sleep whilst holding to avoid
CONFIG_PREEMPT complaining. I have lightly tested preempt on SMP with
the new patch, and it seems to work
regards
john
--
"That's just kitten-eating wrong."
- Richard Henderson
next reply other threads:[~2002-10-13 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 19:38 John Levon [this message]
2002-10-13 20:09 ` 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=20021013193838.GA95824@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=akpm@digeo.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
/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®