Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5
Mark_H_Johnson_at_raytheon.com
Date: 08/31/04
- Previous message: Lee Revell: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Maybe in reply to: Ingo Molnar: "[patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Next in thread: Ingo Molnar: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Reply: Ingo Molnar: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Ingo Molnar <mingo@elte.hu> Date: Tue, 31 Aug 2004 15:10:41 -0500
>since the latency tracer does not trigger, we need a modified tracer to
>find out what's happening during such long delays. I've attached the
>'user-latency-tracer' patch ontop of -Q5, which is a modification of the
>latency tracer.
Grr. I should have checked before I built with this patch. With this in
I now get the
kernel: Could not allocate 4 bytes percpu data
messages again. Need to increase that data area so
#define PERCPU_ENOUGH_ROOM 196608
or something similar (should leave about 50K free for modules).
I will rebuild with this change plus the latest of the others.
--Mark H Johnson
<mailto:Mark_H_Johnson@raytheon.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Lee Revell: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Maybe in reply to: Ingo Molnar: "[patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Next in thread: Ingo Molnar: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Reply: Ingo Molnar: "Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
