From: David Brown <dave@codewhore.org>
To: Robert Love <rml@tech9.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preempt on PowerPC/SMP appears to leak memory
Date: Sun, 13 Apr 2003 22:26:18 -0400 [thread overview]
Message-ID: <20030414022618.GA8993@codewhore.org> (raw)
In-Reply-To: <1050271044.767.7.camel@localhost>
On Sun, Apr 13, 2003 at 05:57:24PM -0400, Robert Love wrote:
| On Sat, 2003-04-12 at 11:29, David Brown wrote:
|
| > I recently applied the preempt-kernel-rml-2.4.21-pre1-1.patch from
| > kernel.org to BenH's stable tree from rsync.penguinppc.org.
|
| Oh, one other thing. An updated patch for 2.4.20 is up:
|
| http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.20-2.patch
|
| It has a couple fixes for proper protection of per-CPU data, including
| some PPC-specific ones.
Hi Robert:
AFAICT, the leak is still there. I'll be looking at that in a bit. I
used the following to get it to compile on the PPC box. I'm not sure if
it's 100% correct, but it appears to work:
diff -ur linux-2.4.20-preempt/arch/ppc/kernel/mk_defs.c linux-2.4.20-ben/arch/ppc/kernel/mk_defs.c
--- linux-2.4.20-preempt/arch/ppc/kernel/mk_defs.c 2003-04-12 02:57:31.000000000 -0400
+++ linux-2.4.20-ben/arch/ppc/kernel/mk_defs.c 2003-04-13 13:57:00.000000000 -0400
@@ -44,6 +44,7 @@
DEFINE(MM, offsetof(struct task_struct, mm));
#ifdef CONFIG_PREEMPT
DEFINE(PREEMPT_COUNT, offsetof(struct task_struct, preempt_count));
+ DEFINE(CPU, offsetof(struct task_struct, processor));
#endif
DEFINE(ACTIVE_MM, offsetof(struct task_struct, active_mm));
DEFINE(TASK_STRUCT_SIZE, sizeof(struct task_struct));
It just adds a DEFINE() for the use of CPU() in arch/ppc/kernel/entry.S.
Thanks,
- Dave
prev parent reply other threads:[~2003-04-14 2:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 15:29 Preempt on PowerPC/SMP appears to leak memory David Brown
2003-04-13 21:55 ` Robert Love
2003-04-13 21:57 ` Robert Love
2003-04-13 22:02 ` David Brown
2003-04-13 23:03 ` Marc-Christian Petersen
2003-04-13 23:07 ` Robert Love
2003-04-13 23:12 ` Marc-Christian Petersen
2003-04-14 2:26 ` David Brown [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=20030414022618.GA8993@codewhore.org \
--to=dave@codewhore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.