From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: [PATCH -mm] i386 syscall opcode reordering (pipelining)
Date: Tue, 13 Jun 2006 21:54:46 +0200 [thread overview]
Message-ID: <20060613195446.GD24167@rhlx01.fht-esslingen.de> (raw)
Hi all,
I'd guess that this version features improved pipeline parallelism,
since we isolate competing %ebx accesses (_syscall4()) and
stack push operations (_syscall5()), right?
Signed-off-by: Andreas Mohr <andi@lisas.de>
diff -urN linux-2.6.17-rc6-mm2.orig/include/asm-i386/unistd.h linux-2.6.17-rc6-mm2.my/include/asm-i386/unistd.h
--- linux-2.6.17-rc6-mm2.orig/include/asm-i386/unistd.h 2006-06-13 19:28:15.000000000 +0200
+++ linux-2.6.17-rc6-mm2.my/include/asm-i386/unistd.h 2006-06-13 19:40:07.000000000 +0200
@@ -400,7 +400,7 @@
type name (type1 arg1,type2 arg2,type3 arg3,type4 arg4,type5 arg5) \
{ \
long __res; \
-__asm__ volatile ("push %%ebx ; movl %2,%%ebx ; movl %1,%%eax ; " \
+__asm__ volatile ("push %%ebx ; movl %1,%%eax ; movl %2,%%ebx ; " \
"int $0x80 ; pop %%ebx" \
: "=a" (__res) \
: "i" (__NR_##name),"ri" ((long)(arg1)),"c" ((long)(arg2)), \
@@ -415,8 +415,8 @@
{ \
long __res; \
struct { long __a1; long __a6; } __s = { (long)arg1, (long)arg6 }; \
-__asm__ volatile ("push %%ebp ; push %%ebx ; movl 4(%2),%%ebp ; " \
- "movl 0(%2),%%ebx ; movl %1,%%eax ; int $0x80 ; " \
+__asm__ volatile ("push %%ebp ; movl %1,%%eax ; push %%ebx ; " \
+ "movl 4(%2),%%ebp ; movl 0(%2),%%ebx ; int $0x80 ; " \
"pop %%ebx ; pop %%ebp" \
: "=a" (__res) \
: "i" (__NR_##name),"0" ((long)(&__s)),"c" ((long)(arg2)), \
next reply other threads:[~2006-06-13 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 19:54 Andreas Mohr [this message]
2006-06-13 20:09 ` Arjan van de Ven
2006-06-13 22:11 ` H. Peter Anvin
2006-06-13 22:15 ` David Woodhouse
2006-06-13 22:21 ` H. Peter Anvin
2006-06-14 19:28 ` Andreas Mohr
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=20060613195446.GD24167@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®