public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Francois Wellenreiter <Francois.Wellenreiter@Ext.Bull.Net>
To: linux-ia64@vger.kernel.org
Subject: INIT handler modification
Date: Fri, 07 Jan 2005 14:13:31 +0000	[thread overview]
Message-ID: <41DE990B.702@Ext.Bull.Net> (raw)


				Dear all,


	first of all, my best wishes for this new year.
Second, I just wanted to start a discussion about INIT handler 
considerations.
Here is the main point, the present code of INIT handler for slave CPUs 
is reduced
to (file arch/ia64/kernel/mca_asm.S) :
______________________________

GLOBAL_ENTRY(ia64_slave_init_handler)
1:      br.sptk 1b
END(ia64_slave_init_handler)
______________________________

I think that when the kernel is deadlocked on another CPU than the 
monarch one,
the traces may be a bit short when I push on the "DUMP" button to have a 
complete
diagnosis of my system.

Thus, I propose you to change the following code (file 
arch/ia64/kernel/mca.c)
______________________________

void __init
ia64_mca_init(void)
{
         ia64_fptr_t *mon_init_ptr = (ia64_fptr_t 
*)ia64_monarch_init_handler;
         ia64_fptr_t *slave_init_ptr = (ia64_fptr_t 
*)ia64_slave_init_handler;
.....
______________________________

into

______________________________

void __init
ia64_mca_init(void)
{
         ia64_fptr_t *mon_init_ptr = (ia64_fptr_t 
*)ia64_monarch_init_handler;
         ia64_fptr_t *slave_init_ptr = (ia64_fptr_t 
*)ia64_monarch_init_handler;
.....
______________________________

What do you think about it ? Do you fear it may induce an unwanted 
behavior towards MCA handling ?

Best regards,

					Francois WELLENREITER


             reply	other threads:[~2005-01-07 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 14:13 Francois Wellenreiter [this message]
2005-01-07 17:51 ` INIT handler modification Bjorn Helgaas
2005-01-07 23:57 ` Luck, Tony
2005-01-08  1:26 ` Keith Owens
2005-01-09 17:21 ` Russ Anderson

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=41DE990B.702@Ext.Bull.Net \
    --to=francois.wellenreiter@ext.bull.net \
    --cc=linux-ia64@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