From: Brian Gerst <brgerst@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/5] x86, 32-bit: Use same regs as 64-bit for kernel_thread_helper
Date: Wed, 9 Dec 2009 12:34:42 -0500 [thread overview]
Message-ID: <1260380084-3707-4-git-send-email-brgerst@gmail.com> (raw)
In-Reply-To: <1260380084-3707-1-git-send-email-brgerst@gmail.com>
The arg should be in %eax, but that is clobbered by the return value
of clone. The function pointer can be in any register. Also, don't
push args onto the stack, since regparm(3) is the normal calling
convention now.
Signed-off-by: Brian Gerst <brgerst@gmail.com>
---
arch/x86/kernel/entry_32.S | 8 ++------
arch/x86/kernel/process_32.c | 8 ++++----
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kernel/entry_32.S b/arch/x86/kernel/entry_32.S
index 50b9c22..0507b02 100644
--- a/arch/x86/kernel/entry_32.S
+++ b/arch/x86/kernel/entry_32.S
@@ -1008,12 +1008,8 @@ END(spurious_interrupt_bug)
ENTRY(kernel_thread_helper)
pushl $0 # fake return address for unwinder
CFI_STARTPROC
- movl %edx,%eax
- push %edx
- CFI_ADJUST_CFA_OFFSET 4
- call *%ebx
- push %eax
- CFI_ADJUST_CFA_OFFSET 4
+ movl %edi,%eax
+ call *%esi
call do_exit
ud2 # padding for call trace
CFI_ENDPROC
diff --git a/arch/x86/kernel/process_32.c b/arch/x86/kernel/process_32.c
index 075580b..ee0d4bc 100644
--- a/arch/x86/kernel/process_32.c
+++ b/arch/x86/kernel/process_32.c
@@ -193,8 +193,8 @@ void show_regs(struct pt_regs *regs)
}
/*
- * This gets run with %bx containing the
- * function to call, and %dx containing
+ * This gets run with %si containing the
+ * function to call, and %di containing
* the "args".
*/
extern void kernel_thread_helper(void);
@@ -208,8 +208,8 @@ int kernel_thread(int (*fn)(void *), void *arg, unsigned long flags)
memset(®s, 0, sizeof(regs));
- regs.bx = (unsigned long) fn;
- regs.dx = (unsigned long) arg;
+ regs.si = (unsigned long) fn;
+ regs.di = (unsigned long) arg;
regs.ds = __USER_DS;
regs.es = __USER_DS;
--
1.6.5.2
next prev parent reply other threads:[~2009-12-09 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 17:34 [PATCH 0/5] x86: Merge kernel_thread() Brian Gerst
2009-12-09 17:34 ` [PATCH 1/5] x86, 64-bit: Move kernel_thread to C Brian Gerst
2009-12-11 0:45 ` [tip:x86/asm] " tip-bot for Brian Gerst
2009-12-09 17:34 ` [PATCH 2/5] x86, 64-bit: Use user_mode() to determine new stack pointer in copy_thread() Brian Gerst
2009-12-11 0:45 ` [tip:x86/asm] " tip-bot for Brian Gerst
2009-12-09 17:34 ` Brian Gerst [this message]
2009-12-11 0:46 ` [tip:x86/asm] x86, 32-bit: Use same regs as 64-bit for kernel_thread_helper tip-bot for Brian Gerst
2009-12-09 17:34 ` [PATCH 4/5] x86: Sync 32/64-bit kernel_thread Brian Gerst
2009-12-11 0:46 ` [tip:x86/asm] " tip-bot for Brian Gerst
2009-12-09 17:34 ` [PATCH 5/5] x86: Merge kernel_thread() Brian Gerst
2009-12-11 0:46 ` [tip:x86/asm] " tip-bot for Brian Gerst
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=1260380084-3707-4-git-send-email-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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