From: Brian Gerst <brgerst@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] x86: Merge kernel_thread()
Date: Wed, 9 Dec 2009 12:34:39 -0500 [thread overview]
Message-ID: <1260380084-3707-1-git-send-email-brgerst@gmail.com> (raw)
[PATCH 1/5] x86, 64-bit: Move kernel_thread to C
[PATCH 2/5] x86, 64-bit: Use user_mode() to determine new stack pointer in copy_thread()
[PATCH 3/5] x86, 32-bit: Use same regs as 64-bit for kernel_thread_helper
[PATCH 4/5] x86: Sync 32/64-bit kernel_thread
[PATCH 5/5] x86: Merge kernel_thread()
arch/x86/kernel/entry_32.S | 8 +----
arch/x86/kernel/entry_64.S | 49 ++-----------------------------------
arch/x86/kernel/process.c | 35 +++++++++++++++++++++++++++
arch/x86/kernel/process_32.c | 33 -------------------------
arch/x86/kernel/process_64.c | 7 ++---
arch/x86/kernel/x8664_ksyms_64.c | 2 -
6 files changed, 43 insertions(+), 91 deletions(-)
next 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 Brian Gerst [this message]
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 ` [PATCH 3/5] x86, 32-bit: Use same regs as 64-bit for kernel_thread_helper Brian Gerst
2009-12-11 0:46 ` [tip:x86/asm] " 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-1-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