From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 2.6.8-rc1] IA64_MCA_DEBUG_INFO
Date: Mon, 12 Jul 2004 02:56:58 +0000 [thread overview]
Message-ID: <4577.1089601018@kao2.melbourne.sgi.com> (raw)
Am I the only person that builds with IA64_MCA_DEBUG_INFO?
Signed-off-by: Keith Owens <kaos@sgi.com>
Note: The first hunk is already in ia64 bk, but not in Linus's bk.
Index: 2.6.8-rc1-pristine/arch/ia64/kernel/mca.c
=================================--- 2.6.8-rc1-pristine.orig/arch/ia64/kernel/mca.c Mon Jul 12 09:22:22 2004
+++ 2.6.8-rc1-pristine/arch/ia64/kernel/mca.c Mon Jul 12 12:48:52 2004
@@ -247,7 +247,9 @@ ia64_mca_log_sal_error_record(int sal_in
u8 *buffer;
u64 size;
int irq_safe = sal_info_type != SAL_INFO_TYPE_MCA && sal_info_type != SAL_INFO_TYPE_INIT;
+#ifdef IA64_MCA_DEBUG_INFO
static const char * const rec_name[] = { "MCA", "INIT", "CMC", "CPE" };
+#endif
size = ia64_log_get(sal_info_type, &buffer, irq_safe);
if (!size)
@@ -596,7 +598,7 @@ ia64_mca_cmc_vector_disable (void *dummy
cmcv = (cmcv_reg_t)ia64_getreg(_IA64_REG_CR_CMCV);
cmcv.cmcv_mask = 1; /* Mask/disable interrupt */
- ia64_setreg(_IA64_REG_CR_CMCV, cmcv.cmcv_regval)
+ ia64_setreg(_IA64_REG_CR_CMCV, cmcv.cmcv_regval);
IA64_MCA_DEBUG("%s: CPU %d corrected "
"machine check vector %#x disabled.\n",
@@ -623,7 +625,7 @@ ia64_mca_cmc_vector_enable (void *dummy)
cmcv = (cmcv_reg_t)ia64_getreg(_IA64_REG_CR_CMCV);
cmcv.cmcv_mask = 0; /* Unmask/enable interrupt */
- ia64_setreg(_IA64_REG_CR_CMCV, cmcv.cmcv_regval)
+ ia64_setreg(_IA64_REG_CR_CMCV, cmcv.cmcv_regval);
IA64_MCA_DEBUG("%s: CPU %d corrected "
"machine check vector %#x enabled.\n",
next reply other threads:[~2004-07-12 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 2:56 Keith Owens [this message]
2004-07-12 20:29 ` [patch 2.6.8-rc1] IA64_MCA_DEBUG_INFO David Mosberger
2004-07-12 21:12 ` Keith Owens
2004-07-12 21:29 ` David Mosberger
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=4577.1089601018@kao2.melbourne.sgi.com \
--to=kaos@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