From: Catalin Marinas <catalin.marinas@arm.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org, David Miller <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC][CFT][CFReview] execve and kernel_thread unification work
Date: Fri, 5 Oct 2012 17:07:47 +0100 [thread overview]
Message-ID: <CAHkRjk6oaZh643hciXyVbvq74KTWgZjfKhyZW1gi8oNEMw3h-A@mail.gmail.com> (raw)
In-Reply-To: <20121001213809.GA31155@ZenIV.linux.org.uk>
Al,
On 1 October 2012 22:38, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Right now the tree lives in
> git.kernel.org/pub/scm/linux/kernel/git/viro/signal experimental-kernel_thread
> Some of that had been in -next for a while.
>
> Folks, help with review, testing and filling the missing bits, please.
I tested this branch with the arm64 kernel and runs ok (I get couple
of compiler warnings because reparent_to_kthread and
__set_special_pids are no longer used with the removal of daemonize).
I have three arm64 patches on this branch:
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git execve
Catalin Marinas (3):
arm64: Use generic kernel_thread() implementation
arm64: Use generic kernel_execve() implementation
arm64: Use generic sys_execve() implementation
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/processor.h | 5 --
arch/arm64/include/asm/syscalls.h | 3 -
arch/arm64/include/asm/unistd.h | 3 +
arch/arm64/kernel/entry.S | 28 ++++++++++---
arch/arm64/kernel/process.c | 78 +++++++++++------------------------
arch/arm64/kernel/sys.c | 65 ------------------------------
arch/arm64/kernel/sys32.S | 7 +---
arch/arm64/kernel/sys_compat.c | 18 --------
9 files changed, 52 insertions(+), 156 deletions(-)
--
Catalin
next prev parent reply other threads:[~2012-10-05 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 21:38 [RFC][CFT][CFReview] execve and kernel_thread unification work Al Viro
2012-10-05 16:07 ` Catalin Marinas [this message]
2012-10-06 16:19 ` Al Viro
2012-10-09 19:48 ` Chris Metcalf
2012-10-10 4:51 ` Al Viro
2012-10-11 9:00 ` Paul Mackerras
2012-10-11 12:53 ` Al Viro
2012-10-12 0:16 ` Paul Mackerras
2012-10-12 1:09 ` [git pull] signal.git, pile 2 (was Re: [RFC][CFT][CFReview] execve and kernel_thread unification work) Al Viro
2012-10-12 5:32 ` Paul Mackerras
2012-10-12 7:55 ` Benjamin Herrenschmidt
2012-10-15 1:30 ` [RFC][CFT][CFReview] execve and kernel_thread unification work Al Viro
2012-10-17 6:16 ` Greg Ungerer
2012-10-17 14:02 ` Catalin Marinas
2012-10-17 16:34 ` Al Viro
2012-10-17 16:40 ` Catalin Marinas
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=CAHkRjk6oaZh643hciXyVbvq74KTWgZjfKhyZW1gi8oNEMw3h-A@mail.gmail.com \
--to=catalin.marinas@arm.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).