From: Ingo Molnar <mingo@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic
Date: Tue, 12 May 2015 09:02:39 +0200 [thread overview]
Message-ID: <20150512070239.GA30476@gmail.com> (raw)
In-Reply-To: <20150511192810.GA11328@jtriplet-mobl1>
* Josh Triplett <josh@joshtriplett.org> wrote:
> clone has some of the quirkiest syscall handling in the kernel, with
> a pile of special cases, historical curiosities, and
> architecture-specific calling conventions. In particular, clone
> with CLONE_SETTLS accepts a parameter "tls" that the C entry point
> completely ignores and some assembly entry points overwrite;
> instead, the low-level arch-specific code pulls the tls parameter
> out of the arch-specific register captured as part of pt_regs on
> entry to the kernel. That's a massive hack, and it makes the
> arch-specific code only work when called via the specific existing
> syscall entry points; because of this hack, any new clone-like
> system call would have to accept an identical tls argument in
> exactly the same arch-specific position, rather than providing a
> unified system call entry point across architectures.
>
> The first patch allows architectures to handle the tls argument via
> normal C parameter passing, if they opt in by selecting
> HAVE_COPY_THREAD_TLS. The second patch makes 32-bit and 64-bit x86
> opt into this.
>
> These two patches came out of the clone4 series, which isn't ready
> for this merge window, but these first two cleanup patches were
> entirely uncontroversial and have acks. I'd like to go ahead and
> submit these two so that other architectures can begin building on
> top of this and opting into HAVE_COPY_THREAD_TLS. However, I'm also
> happy to wait and send these through the next merge window (along
> with v3 of clone4) if anyone would prefer that.
>
> v2: Move co-author from signoffs to a note in the commit message, as
> required by Ingo Molnar.
>
> Josh Triplett (2):
> clone: Support passing tls argument via C rather than pt_regs magic
> x86: Opt into HAVE_COPY_THREAD_TLS, for both 32-bit and 64-bit
>
> arch/Kconfig | 7 ++++++
> arch/x86/Kconfig | 1 +
> arch/x86/ia32/ia32entry.S | 2 +-
> arch/x86/kernel/process_32.c | 6 ++---
> arch/x86/kernel/process_64.c | 8 +++----
> include/linux/sched.h | 14 +++++++++++
> include/linux/syscalls.h | 6 ++---
> kernel/fork.c | 55 +++++++++++++++++++++++++++++---------------
> 8 files changed, 69 insertions(+), 30 deletions(-)
So I have no objections if Linus doesn't see a cleaner/better
approach.
Thanks,
Ingo
prev parent reply other threads:[~2015-05-12 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:28 [PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic Josh Triplett
2015-05-12 7:02 ` Ingo Molnar [this message]
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=20150512070239.GA30476@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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