From: Denys Vlasenko <dvlasenk@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Alexei Starovoitov <ast@plumgrid.com>,
Will Drewry <wad@chromium.org>, Kees Cook <keescook@chromium.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] x86/asm/entry/32: Explain stub32_clone logic
Date: Wed, 3 Jun 2015 15:58:49 +0200 [thread overview]
Message-ID: <1433339930-20880-1-git-send-email-dvlasenk@redhat.com> (raw)
The reason for copying of %r8 to %rcx is quite non-obvious.
Add a comment which explains why it is done.
Fix indentation and trailing whitespace while at it.
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
CC: Linus Torvalds <torvalds@linux-foundation.org>
CC: Steven Rostedt <rostedt@goodmis.org>
CC: Ingo Molnar <mingo@kernel.org>
CC: Borislav Petkov <bp@alien8.de>
CC: "H. Peter Anvin" <hpa@zytor.com>
CC: Andy Lutomirski <luto@amacapital.net>
CC: Oleg Nesterov <oleg@redhat.com>
CC: Frederic Weisbecker <fweisbec@gmail.com>
CC: Alexei Starovoitov <ast@plumgrid.com>
CC: Will Drewry <wad@chromium.org>
CC: Kees Cook <keescook@chromium.org>
CC: x86@kernel.org
CC: linux-kernel@vger.kernel.org
---
This is a resend.
arch/x86/ia32/ia32entry.S | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
index 2ca052e..8e72256 100644
--- a/arch/x86/ia32/ia32entry.S
+++ b/arch/x86/ia32/ia32entry.S
@@ -562,9 +562,17 @@ GLOBAL(\label)
ALIGN
GLOBAL(stub32_clone)
- leaq sys_clone(%rip),%rax
+ leaq sys_clone(%rip), %rax
+ /*
+ * 32-bit clone API is clone(..., int tls_val, int *child_tidptr).
+ * 64-bit clone API is clone(..., int *child_tidptr, int tls_val).
+ * Native 64-bit kernel's sys_clone() implements the latter.
+ * We need to swap args here. But since tls_val is in fact ignored
+ * by sys_clone(), we can get away with an assignment
+ * (arg4 = arg5) instead of a full swap:
+ */
mov %r8, %rcx
- jmp ia32_ptregs_common
+ jmp ia32_ptregs_common
ALIGN
ia32_ptregs_common:
--
1.8.1.4
next reply other threads:[~2015-06-03 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 13:58 Denys Vlasenko [this message]
2015-06-03 13:58 ` [PATCH 2/2] x86/asm/entry/32: Remove unnecessary optimization in stub32_clone Denys Vlasenko
2015-06-03 16:38 ` Josh Triplett
2015-06-04 10:07 ` Denys Vlasenko
2015-06-04 15:58 ` Josh Triplett
2015-06-05 11:44 ` Ingo Molnar
2015-06-07 8:32 ` [tip:x86/asm] " tip-bot for Denys Vlasenko
2015-06-07 8:32 ` [tip:x86/asm] x86/asm/entry/32: Explain the stub32_clone logic tip-bot for Denys Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2015-04-22 16:40 [PATCH 1/2] x86/asm/entry/32: Explain " Denys Vlasenko
2015-04-22 16:53 ` Andy Lutomirski
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=1433339930-20880-1-git-send-email-dvlasenk@redhat.com \
--to=dvlasenk@redhat.com \
--cc=ast@plumgrid.com \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=wad@chromium.org \
--cc=x86@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®