linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luotao Fu <l.fu@pengutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt2
Date: Tue, 15 Jan 2008 17:27:29 +0100	[thread overview]
Message-ID: <20080115162729.GF5859@pengutronix.de> (raw)
In-Reply-To: <1200336080.318.8.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2655 bytes --]

Hi,

On Mon, Jan 14, 2008 at 01:41:20PM -0500, Steven Rostedt wrote:
> We are pleased to announce the 2.6.24-rc7-rt2 tree, which can be
> downloaded from the location:
> 
>   http://rt.et.redhat.com/download/
> 
.......... 
> Changes since 2.6.24-rc7-rt1
> 
 
..........
>   - PPC compile fix (reported by: Robert Schwebel)
> 

Compiling with tracing function turned seemed still to be broken to me:
kernel/built-in.o: In function `early_printk_name':
latency_trace.c:(.text+0x3cd18): undefined reference to `early_printk'
latency_trace.c:(.text+0x3cd40): undefined reference to `early_printk'
kernel/built-in.o: In function `early_print_entry':
latency_trace.c:(.text+0x3cd80): undefined reference to `early_printk'
latency_trace.c:(.text+0x3cdd8): undefined reference to `early_printk'
latency_trace.c:(.text+0x3cdfc): undefined reference to `early_printk'

We made a early_printk patch based on the 8250_early for powerpc 32bit here.
(still absolutely untested and incomplete, we will post it asap). I added
early_printk() and exported _mcount() and could compile succesfully. However the
kernel will not boot. I attached a bdi to it and found out that it stucks at
_mcount in arch/powerpc/kernel/entry_32.S at about line 1080, where the variable
mcount_enabled is loaded and checked. Obviously the variable is still not valid
at the time of check. To check this I took out the lines like above

--- arch/powerpc/kernel/entry_32.S.orig 2008-01-15 17:01:25.000000000 +0100
+++ arch/powerpc/kernel/entry_32.S      2008-01-15 17:17:18.000000000 +0100
@@ -1075,9 +1075,6 @@
        stw     r6, 24(r1)
        mflr    r3      /* will use as first arg to __trace() */
        mfcr    r4
-       lis     r5,mcount_enabled@ha
-       lwz     r5,mcount_enabled@l(r5)
-       cmpwi   r5,0
        stw     r3, 44(r1)      /* lr */
        stw     r4,  8(r1)      /* cr */
        stw     r7, 28(r1)

After recompiling the kernel started normally and it seems to work. I was even
able to make a trace with cyclictest. However there were several crashes (which
might be caused by other problems). I still have to take a closer look.

I am just wondering why the check for mcount_enabled is there at all and I think
that there due to be some better fixes than just throw it out ;-). On the other
side, I just can't find in which way mcount_enabled is used in the tracer at
all. Could you give me some hints on this one?

cheers
Luotao Fu
-- 
   Dipl.-Ing. Luotao Fu | Phone: +49-5121-206917-3
Pengutronix - Linux Solutions for Science and Industry
Entwicklungszentrum Nord     http://www.pengutronix.de


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-01-15 16:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 18:41 2.6.24-rc7-rt2 Steven Rostedt
2008-01-14 20:02 ` 2.6.24-rc7-rt2 Mark Knecht
2008-01-14 22:16 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-14 22:30   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 17:10     ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17  2:07       ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:11         ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 17:25           ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:57             ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-15  0:37 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16  3:50   ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16  4:04     ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16  6:23       ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 14:12         ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 16:22           ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-21 11:31             ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-21 12:49               ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-27 21:51                 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-28  2:32               ` 2.6.24-rc7-rt2 Stefan Monnier
2008-01-16 13:17     ` 2.6.24-rc7-rt2 Alan Cox
2008-01-16  4:01   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16  7:12     ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 10:11       ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-17  2:20         ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15  3:44 ` 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz() Mike Galbraith
2008-01-15 16:27 ` Luotao Fu [this message]
2008-01-15 18:06   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 20:04     ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-16 12:03     ` 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32 Luotao Fu
2008-01-17  3:26       ` Steven Rostedt

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=20080115162729.GF5859@pengutronix.de \
    --to=l.fu@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).