From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <KevinK@mips.com>
Cc: linux-mips@linux-mips.org, Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: [PATCH] ret_from_irq adjustment
Date: Mon, 9 Oct 2006 14:53:33 +0100 [thread overview]
Message-ID: <20061009135332.GA14048@linux-mips.org> (raw)
In-Reply-To: <006501c6eb07$4fbf66c0$8003a8c0@Ulysses>
On Sun, Oct 08, 2006 at 08:26:44PM +0200, Kevin D. Kissell wrote:
> While setting up ra "by hand" and transferring control via the jr
> is a reasonable optimization, you're otherwise breaking things for SMTC.
> While the comments are misleading (they accurately described an earlier
> version of the code), the function being called here is ipi_decode(), which
> needs a pt_regs * in the first argument (hence the copy of the sp), and
> the pointer to the IPI message descriptor in the second.
>
> Do you have access to a 34K to test changes to SMTC? I'd have
> expected this one to have been pretty quickly fatal.
Second reply after a closer look at the patch.
ipi_decode() has lost it's pt_regs argument like most of the interrupt
related functions, so Atushi's patch was right. Any interrupt handler
that wants to get a pointer to the register frame can do so by calling
get_irq_regs().
The cleanup did actually work so well I'm tempted to use the same
strategy also for the CU and RI exception handlers which would make the
FPU exception handler look a whole lot more friendly.
So with Atsushi's patch applied VSMP and SMTC with only two TCs activated
are working again. It still crashes with 5 TCs enabled:
Cpu 1
$ 0 : 00000000 18102000 00000000 8041ed44
$ 4 : 00000000 00000000 8041ec88 00000000
$ 8 : 00000000 18001c00 8010de78 80430000
$12 : 80420000 fffffffb ffffffff 0000000a
$16 : 00000000 00000001 8041ec04 8041ec08
$20 : 803b0000 8041ed40 80380000 18102000
$24 : 00000000 810c3b11
$28 : 810c2000 810c3b58 00000100 80108bdc
Hi : 00000009
Lo : fbe7d600
epc : 80132b74 profile_tick+0x20/0xb4 Not tainted
ra : 80108bdc local_timer_interrupt+0x10/0x30
Status: 1100a603 KERNEL EXL IE
Ralf
next prev parent reply other threads:[~2006-10-09 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 16:24 [PATCH] ret_from_irq adjustment Atsushi Nemoto
2006-10-08 18:26 ` Kevin D. Kissell
2006-10-08 18:26 ` Kevin D. Kissell
2006-10-08 21:44 ` Ralf Baechle
2006-10-09 10:43 ` Kevin D. Kissell
2006-10-09 10:43 ` Kevin D. Kissell
2006-10-09 13:53 ` Ralf Baechle [this message]
2006-10-09 14:40 ` Atsushi Nemoto
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=20061009135332.GA14048@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=KevinK@mips.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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