From: "Kip Walker" <kwalker@broadcom.com>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: scall_n32.S register saves
Date: Fri, 07 Mar 2003 11:29:34 -0800 [thread overview]
Message-ID: <3E68F31E.76604C00@broadcom.com> (raw)
If O32 is enabled, handle_sysn32 shouldn't have to SAVE_SOME and STI...
Kip
Index: arch/mips64/kernel/scall_n32.S
===================================================================
RCS file: /home/cvs/linux/arch/mips64/kernel/scall_n32.S,v
retrieving revision 1.2.2.8
diff -u -r1.2.2.8 scall_n32.S
--- arch/mips64/kernel/scall_n32.S 7 Mar 2003 01:22:48 -0000
1.2.2.8
+++ arch/mips64/kernel/scall_n32.S 7 Mar 2003 19:27:50 -0000
@@ -29,6 +29,12 @@
.align 5
NESTED(handle_sysn32, PT_SIZE, sp)
+#ifndef CONFIG_MIPS32_O32
+ .set noat
+ SAVE_SOME
+ STI
+ .set at
+#endif
ld t1, PT_EPC(sp) # skip syscall on return
subu t0, v0, __NR_N32_Linux # check syscall number
reply other threads:[~2003-03-07 19:42 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=3E68F31E.76604C00@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.