From: Chris Metcalf <cmetcalf@tilera.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: Tue, 9 Oct 2012 15:48:16 -0400 [thread overview]
Message-ID: <50747F80.4060503@tilera.com> (raw)
In-Reply-To: <20121001213809.GA31155@ZenIV.linux.org.uk>
On 10/1/2012 5:38 PM, Al Viro wrote:
> There's an interesting ongoing project around kernel_thread() and
> friends, including execve() variants. I really need help from architecture
> maintainers on that one; I'd been able to handle (and test) quite a few
> architectures on my own [alpha, arm, m68k, powerpc, s390, sparc, x86, um]
> plus two more untested [frv, mn10300]. c6x patches had been supplied by
> Mark Salter; everything else remains to be done. Right now it's at
> minus 1.2KLoC, quite a bit of that removed from asm glue and other black
> magic.
I'll take a look at this for arch/tile this week.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2012-10-09 19:48 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
2012-10-06 16:19 ` Al Viro
2012-10-09 19:48 ` Chris Metcalf [this message]
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=50747F80.4060503@tilera.com \
--to=cmetcalf@tilera.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).