From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH 04/04] sh: prefetch early exception data on sh3/sh4/sh4a
Date: Mon, 23 Feb 2009 07:19:31 +0000 [thread overview]
Message-ID: <20090223071931.12300.72669.sendpatchset@rx1.opensource.se> (raw)
From: Magnus Damm <damm@igel.co.jp>
Prefetch early exception data. There is unused space in our
exception handler cache line anyway, so this is almost free.
Signed-off-by: Magnus Damm <damm@igel.co.jp>
---
arch/sh/kernel/cpu/sh3/entry.S | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
--- 0007/arch/sh/kernel/cpu/sh3/entry.S
+++ work/arch/sh/kernel/cpu/sh3/entry.S 2009-02-23 14:18:48.000000000 +0900
@@ -463,9 +463,11 @@ tlb_miss:
sts pr, k3 ! save original pr value in k3
handle_exception:
+ mova exception_data, k0
+
! Setup stack and save DSP context (k0 contains original r15 on return)
bsr prepare_stack_save_dsp
- nop
+ pref @k0
! Save registers / Switch to bank 0
mov.l 5f, k2 ! vector register address
@@ -556,10 +558,11 @@ ENTRY(handle_interrupt)
11:
#endif /* defined(CONFIG_KGDB) */
sts pr, k3 ! save original pr value in k3
+ mova exception_data, k0
! Setup stack and save DSP context (k0 contains original r15 on return)
bsr prepare_stack_save_dsp
- nop
+ pref @k0
! Save registers / Switch to bank 0
bsr save_regs ! needs original pr value in k3
next reply other threads:[~2009-02-23 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 7:19 Magnus Damm [this message]
2009-02-27 7:22 ` [PATCH 04/04] sh: prefetch early exception data on sh3/sh4/sh4a Paul Mundt
2009-02-27 7:53 ` Magnus Damm
2009-03-02 2:30 ` Paul Mundt
2009-03-02 2:47 ` Paul Mundt
2009-03-02 2:48 ` Magnus Damm
2009-03-02 2:55 ` Magnus Damm
2009-03-16 12:00 ` Kristoffer Ericson
2009-03-16 12:50 ` Paul Mundt
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=20090223071931.12300.72669.sendpatchset@rx1.opensource.se \
--to=magnus.damm@gmail.com \
--cc=linux-sh@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