From: Andi Kleen <ak@suse.de>
To: pageexec@freemail.hu
Cc: Willy Tarreau <w@1wt.eu>,
Riley@williams.name, davej@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] exception processing in early boot
Date: Wed, 30 Aug 2006 18:30:40 +0200 [thread overview]
Message-ID: <200608301830.40994.ak@suse.de> (raw)
In-Reply-To: <44F5D81A.9650.5BE48F99@pageexec.freemail.hu>
On Wednesday 30 August 2006 18:25, pageexec@freemail.hu wrote:
> On 30 Aug 2006 at 14:59, Andi Kleen wrote:
> > > I think that the good method would be to :
> > > - announce the patch
> > > - find a volunteer to port it
> > > - apply it once the volunteer agrees to handle it
> > > This way, no code gets lost because there's always someone to track it.
> >
> > I can put that one into my tree for .19
>
> here's my quick attempt:
It would be better to separate exceptions from interrupts here.
A spurious interrupt is not necessarily fatal, just an exception is.
But I went with the simpler patch with some changes now
(added PANIC to the message etc.)
>
> --- linux-2.6.18-rc5/arch/i386/kernel/head.S 2006-08-28 11:37:31.000000000
> +0200
> +++ linux-2.6.18-rc5-fix/arch/i386/kernel/head.S 2006-08-30
> 18:22:15.000000000 +0200
> @@ -382,34 +382,25 @@ rp_sidt:
> /* This is the default interrupt "handler" :-) */
> ALIGN
> ignore_int:
> - cld
> #ifdef CONFIG_PRINTK
> - pushl %eax
> - pushl %ecx
> - pushl %edx
> - pushl %es
> - pushl %ds
> + cld
> movl $(__KERNEL_DS),%eax
> movl %eax,%ds
> movl %eax,%es
> - pushl 16(%esp)
> - pushl 24(%esp)
> - pushl 32(%esp)
> - pushl 40(%esp)
> + pushl 12(%esp)
> + pushl 12(%esp)
> + pushl 12(%esp)
> + pushl 12(%esp)
> pushl $int_msg
> #ifdef CONFIG_EARLY_PRINTK
> call early_printk
> #else
> call printk
> #endif
> - addl $(5*4),%esp
> - popl %ds
> - popl %es
> - popl %edx
> - popl %ecx
> - popl %eax
> #endif
> - iret
> +1: hlt
This is wrong because i386 still supports some CPUs that don't support
HLT.
-Andi
next prev parent reply other threads:[~2006-08-30 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 6:39 [PATCH][RFC] exception processing in early boot Willy Tarreau
2006-08-30 9:51 ` Andi Kleen
2006-08-30 12:18 ` Willy Tarreau
2006-08-30 12:59 ` Andi Kleen
2006-08-30 13:16 ` Willy Tarreau
[not found] ` <20060830100015.6b967c32.seanlkml@sympatico.ca>
2006-08-30 13:46 ` Willy Tarreau
2006-08-30 14:00 ` Sean
[not found] ` <44F5D81A.9650.5BE48F99@pageexec.freemail.hu>
2006-08-30 16:30 ` Andi Kleen [this message]
2006-08-30 16:59 ` linux-os (Dick Johnson)
2006-08-30 17:02 ` Andi Kleen
2006-08-30 17:15 ` linux-os (Dick Johnson)
[not found] ` <44F5E818.20898.5C230A79@pageexec.freemail.hu>
2006-08-30 17:52 ` Andi Kleen
[not found] ` <44F5F348.1251.5C4EBCCB@pageexec.freemail.hu>
2006-08-30 18:26 ` Andi Kleen
2006-08-30 19:01 ` Willy Tarreau
2006-08-30 19:36 ` Andi Kleen
2006-08-30 20:03 ` Willy Tarreau
2006-08-30 20:06 ` Andi Kleen
2006-08-30 20:40 ` Willy Tarreau
2006-08-30 21:31 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 2:05 Chuck Ebbert
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=200608301830.40994.ak@suse.de \
--to=ak@suse.de \
--cc=Riley@williams.name \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=w@1wt.eu \
/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