From: Andi Kleen <ak@suse.de>
To: YhLu <YhLu@tyan.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 with dual way dual core ck804 MB
Date: Wed, 22 Jun 2005 01:55:40 +0200 [thread overview]
Message-ID: <20050621235540.GK14251@wotan.suse.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C94314230A4046AA@TYANWEB>
On Tue, Jun 21, 2005 at 03:50:48PM -0700, YhLu wrote:
> I would like to help. Can you say more detail ? I don't know how to souce
> code tracing statement....
>
> Do you mean setup one global buffer, and in the setup.c compare the node id
> or node id to decide to write sth to the buffer, and print out when the cpu0
> get the control again?
Yes. You can just use a global variable because the smp bootup is essentially
single threaded. printk would destroy the timing though.
Start with the code that prints ExtInt enabled.
Writ current_text_address() into a buffer and dump it then on CPU #0
after some timeout (hopefully it is still alive)
If you have problems mail me and I will write you a tracing patch
tomorrow.
-Andi
next prev parent reply other threads:[~2005-06-22 0:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 22:50 YhLu
2005-06-21 23:55 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 1:01 YhLu
2005-06-24 23:47 YhLu
2005-06-29 2:40 ` Eric W. Biederman
2005-06-30 18:54 ` Andrew Vasquez
2005-06-30 20:54 ` Eric W. Biederman
2005-06-24 23:42 YhLu
2005-06-24 23:42 ` Andi Kleen
2005-06-24 18:56 YhLu
2005-06-23 0:07 YhLu
2005-06-23 0:12 ` Andi Kleen
2005-06-22 23:37 YhLu
2005-06-22 23:37 ` Andi Kleen
2005-06-21 22:17 YhLu
2005-06-21 21:41 YhLu
2005-06-21 22:12 ` Andi Kleen
2005-06-22 22:26 ` Peter Buckingham
2005-06-22 23:10 ` Andi Kleen
2005-06-22 23:31 ` Peter Buckingham
2005-06-21 22:36 ` Andi Kleen
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=20050621235540.GK14251@wotan.suse.de \
--to=ak@suse.de \
--cc=YhLu@tyan.com \
--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
all inboxes | Powered by JetHome®