From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC][PATCH] i386: Per node IDT
Date: Mon, 11 Jul 2005 08:03:54 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0507110747480.16055@montezuma.fsmlabs.com> (raw)
In-Reply-To: <42D26604.66A75939@tv-sign.ru>
Hello Oleg,
On Mon, 11 Jul 2005, Oleg Nesterov wrote:
> Zwane Mwaikambo wrote:
> >
> > --- linux-2.6.13-rc1-mm1/arch/i386/kernel/entry.S 3 Jul 2005 13:20:43 -0000 1.1.1.1
> > +++ linux-2.6.13-rc1-mm1/arch/i386/kernel/entry.S 10 Jul 2005 22:33:37 -0000
> > -
> > +/* Build the IRQ entry stubs */
> > vector=0
> > -ENTRY(irq_entries_start)
> > + .align IRQ_STUB_SIZE,0x90
> > +ENTRY(interrupt)
> > .rept NR_IRQS
> > ALIGN
> > -1: pushl $vector-256
> > + pushl $vector
> > jmp common_interrupt
> >
> > [...snip...]
> >
> > --- linux-2.6.13-rc1-mm1/arch/i386/kernel/irq.c 3 Jul 2005 13:20:43 -0000 1.1.1.1
> > +++ linux-2.6.13-rc1-mm1/arch/i386/kernel/irq.c 4 Jul 2005 21:39:56 -0000
> > @@ -53,8 +53,7 @@ static union irq_ctx *softirq_ctx[NR_CPU
> > */
> > fastcall unsigned int do_IRQ(struct pt_regs *regs)
> > {
> > - /* high bits used in ret_from_ code */
> > - int irq = regs->orig_eax & 0xff;
> > + int irq = regs->orig_eax;
>
> Could you explain this change? I think it breaks do_signal/handle_signal,
> they check orig_eax >= 0 to handle -ERESTARTSYS:
>
> /* Are we from a system call? */
> if (regs->orig_eax >= 0) {
> /* If so, check system call restarting.. */
> switch (regs->eax) {
> case -ERESTART_RESTARTBLOCK:
> case -ERESTARTNOHAND:
The change is so that we can send IRQs higher than 256 to do_IRQ. That
looks like it tries to check if we came in via system_call since we'd save
the system call number as orig_eax. Now that i think about it, doesn't
that path always get taken when we interrupt userspace and have pending
signals on return from interrupt?
next prev parent reply other threads:[~2005-07-12 1:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:28 [RFC][PATCH] i386: Per node IDT Oleg Nesterov
2005-07-11 14:03 ` Zwane Mwaikambo [this message]
2005-07-11 14:44 ` Oleg Nesterov
2005-07-11 15:05 ` Zwane Mwaikambo
2005-07-11 15:19 ` Oleg Nesterov
2005-08-07 1:13 ` Zwane Mwaikambo
2005-08-07 10:47 ` Oleg Nesterov
[not found] <Pine.LNX.4.61.0507101617240.16055@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2005-07-11 1:59 ` Andi Kleen
2005-07-11 4:02 ` Arjan van de Ven
2005-07-11 4:08 ` Andi Kleen
2005-07-11 14:09 ` Zwane Mwaikambo
2005-07-11 14:05 ` Arjan van de Ven
2005-07-11 15:17 ` Kenji Kaneshige
2005-07-11 13:34 ` Zwane Mwaikambo
2005-07-11 15:03 ` Brian Gerst
2005-07-11 15:21 ` Zwane Mwaikambo
2005-07-11 16:39 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-07-10 22:41 Zwane Mwaikambo
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=Pine.LNX.4.61.0507110747480.16055@montezuma.fsmlabs.com \
--to=zwane@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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;
as well as URLs for NNTP newsgroup(s).