From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [ia64 R&D] CONFIG_IA64_MCA
Date: Tue, 04 May 2004 16:34:18 +0000 [thread overview]
Message-ID: <200405040934.18544.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <EFC4A8BDEDB4B846BC47F0ED773E812C0734C47C@xsun09.ptp.hp.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Tuesday, May 4, 2004 9:06 am, CURRY,JOHN W (HP-Cupertino,ex1) wrote:
> Yes, I think that could work. Tell me more. I have already communicated
> with Jesse, though.
It might look something like this (though now that I've looked at it, it seems
we could use an early option parser for ia64). I've tried to add a 'nomca'
boot option that you can pass to the kernel to avoid registering the MCA
handlers with the firmware. This kernel builds and boots for me w/o the
'nomca' option, but on sn2 it hangs at boot if I pass 'nomca'.
Jesse
[-- Attachment #2: no-mca-register.patch --]
[-- Type: text/plain, Size: 832 bytes --]
===== arch/ia64/kernel/setup.c 1.70 vs edited =====
--- 1.70/arch/ia64/kernel/setup.c Wed Mar 17 04:46:59 2004
+++ edited/arch/ia64/kernel/setup.c Tue May 4 09:23:34 2004
@@ -283,6 +283,9 @@
void __init
setup_arch (char **cmdline_p)
{
+ char *cp;
+ int nomca = 0;
+
unw_init();
ia64_patch_vtop((u64) __start___vtop_patchlist, (u64) __end___vtop_patchlist);
@@ -359,9 +362,19 @@
conswitchp = &vga_con;
# endif
#endif
-
- /* enable IA-64 Machine Check Abort Handling */
- ia64_mca_init();
+ for (cp = saved_command_line; *cp; )
+ if (memcmp(cp, "nomca", 5) == 0)
+ nomca = 1;
+ else {
+ while (*cp != ' ' && *cp)
+ ++cp;
+ while (*cp == ' ')
+ ++cp;
+ }
+
+ /* enable IA-64 Machine Check Abort Handling unless disabled */
+ if (!nomca)
+ ia64_mca_init();
platform_setup(cmdline_p);
paging_init();
next prev parent reply other threads:[~2004-05-04 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 18:35 FW: [ia64 R&D] CONFIG_IA64_MCA John Curry
2004-05-03 18:41 ` Jesse Barnes
2004-05-04 13:53 ` Luck, Tony
2004-05-04 15:19 ` Jesse Barnes
2004-05-04 16:06 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-04 16:34 ` Jesse Barnes [this message]
2004-05-05 2:51 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 19:57 ` Jesse Barnes
2004-05-07 21:19 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 21:28 ` Chen, Kenneth W
2004-05-07 21:32 ` Jesse Barnes
2004-08-03 13:57 ` Sourav Sen
2004-08-03 16:00 ` Jesse Barnes
2004-08-03 16:43 ` Luck, Tony
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=200405040934.18544.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--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