From: Brian Gerst <bgerst@didntduck.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [PATCH] Small bluesmoke patch
Date: Mon, 03 Dec 2001 23:12:01 -0500 [thread overview]
Message-ID: <3C0C4D11.90D3A46B@didntduck.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 144 bytes --]
This patch eliminates the do_machine_check function, by using the
machine_check_vector directly from the asm entry stub.
--
Brian Gerst
[-- Attachment #2: diff-bluesmoke --]
[-- Type: text/plain, Size: 1196 bytes --]
diff -urN linux-2.5.1-pre2/arch/i386/kernel/bluesmoke.c linux/arch/i386/kernel/bluesmoke.c
--- linux-2.5.1-pre2/arch/i386/kernel/bluesmoke.c Mon Nov 12 12:59:43 2001
+++ linux/arch/i386/kernel/bluesmoke.c Tue Nov 27 15:01:50 2001
@@ -98,16 +98,7 @@
printk(KERN_ERR "CPU#%d: Unexpected int18 (Machine Check).\n", smp_processor_id());
}
-/*
- * Call the installed machine check handler for this CPU setup.
- */
-
-static void (*machine_check_vector)(struct pt_regs *, long error_code) = unexpected_machine_check;
-
-asmlinkage void do_machine_check(struct pt_regs * regs, long error_code)
-{
- machine_check_vector(regs, error_code);
-}
+void (*machine_check_vector)(struct pt_regs *, long error_code) = unexpected_machine_check;
/*
* Set up machine check reporting for Intel processors
diff -urN linux-2.5.1-pre2/arch/i386/kernel/entry.S linux/arch/i386/kernel/entry.S
--- linux-2.5.1-pre2/arch/i386/kernel/entry.S Fri Nov 2 20:18:49 2001
+++ linux/arch/i386/kernel/entry.S Tue Nov 27 15:01:17 2001
@@ -386,7 +386,7 @@
ENTRY(machine_check)
pushl $0
- pushl $ SYMBOL_NAME(do_machine_check)
+ pushl SYMBOL_NAME(machine_check_vector)
jmp error_code
ENTRY(spurious_interrupt_bug)
reply other threads:[~2001-12-04 4:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C0C4D11.90D3A46B@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®