From: Andreas Schwab <schwab@linux-m68k.org>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"Luck, Tony" <tony.luck@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Qais Yousef <qais.yousef@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args
Date: Thu, 14 May 2020 10:37:03 +0000 [thread overview]
Message-ID: <87blmq6bw0.fsf@igel.home> (raw)
In-Reply-To: <20200514101914.fu7xhgaxtb5fy2ky@wittgenstein> (Christian Brauner's message of "Thu, 14 May 2020 12:19:14 +0200")
On Mai 14 2020, Christian Brauner wrote:
>> static inline pid_t raw_clone(unsigned long flags) {
>> pid_t ret;
>>
>> assert((flags & (CLONE_VM|CLONE_PARENT_SETTID|CLONE_CHILD_SETTID|
>> CLONE_CHILD_CLEARTID|CLONE_SETTLS)) = 0);
>> #if defined(__s390x__) || defined(__s390__) || defined(__CRIS__)
>> /* On s390/s390x and cris the order of the first and second arguments
>> * of the raw clone() system call is reversed. */
>> ret = (pid_t) syscall(__NR_clone, NULL, flags);
>> #elif defined(__sparc__)
>> {
>> /**
>> * sparc always returns the other process id in %o0, and
>> * a boolean flag whether this is the child or the parent in
>> * %o1. Inline assembly is needed to get the flag returned
>> * in %o1.
>> */
>> int in_child, child_pid, error;
>>
>> asm volatile("mov %3, %%g1\n\t"
>> "mov %4, %%o0\n\t"
>> "mov 0 , %%o1\n\t"
>> #if defined(__arch64__)
>> "t 0x6d\n\t"
>> #else
>> "t 0x10\n\t"
>> #endif
>> "addx %%g0, 0, %2\n\t"
>> "mov %%o1, %0\n\t"
>> "mov %%o0, %1" :
>> "=r"(in_child), "=r"(child_pid), "=r"(error) :
>> "i"(__NR_clone), "r"(flags) :
>> "%o1", "%o0", "%g1", "cc" );
>>
>> if (error) {
>> errno = child_pid;
>> ret = -1;
>> } else
>> ret = in_child ? 0 : child_pid;
>> }
>> +#elif defined(__ia64__)
>> + /* On ia64 the stack and stack size are passed as separate arguments. */
>> + return (pid_t)syscall(__NR_clone, flags, NULL, 0);
>> +#else
>> + return (pid_t)syscall(__NR_clone, flags, NULL);
>> +#endif
>
> Scratch that. It's even worse. On ia64 it is _invalid_ to pass a NULL
> stack.
Only if you want CLONE_VM. But this raw_clone does not allow CLONE_VM,
thus it is actually a true fork.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-05-14 10:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 20:48 [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args Christian Brauner
2020-05-13 21:19 ` Luck, Tony
2020-05-13 21:26 ` John Paul Adrian Glaubitz
2020-05-14 7:46 ` Christian Brauner
2020-05-14 7:53 ` John Paul Adrian Glaubitz
2020-05-14 7:58 ` Christian Brauner
2020-05-14 8:24 ` John Paul Adrian Glaubitz
2020-05-14 8:37 ` Christian Brauner
2020-05-14 8:51 ` John Paul Adrian Glaubitz
2020-05-14 9:48 ` John Paul Adrian Glaubitz
2020-05-14 10:04 ` Christian Brauner
2020-05-14 10:08 ` John Paul Adrian Glaubitz
2020-05-14 10:15 ` Christian Brauner
2020-05-14 10:19 ` Christian Brauner
2020-05-14 10:21 ` John Paul Adrian Glaubitz
2020-05-14 10:32 ` Christian Brauner
2020-05-14 10:35 ` John Paul Adrian Glaubitz
2020-05-14 10:39 ` Christian Brauner
2020-05-14 10:37 ` Christian Brauner
2020-05-14 10:45 ` Andreas Schwab
2020-05-14 10:51 ` Christian Brauner
2020-05-14 10:37 ` Andreas Schwab [this message]
2020-05-14 13:00 ` Christian Brauner
2020-05-14 8:58 ` Sebastian Andrzej Siewior
2020-05-14 9:57 ` Christian Brauner
2020-05-14 7:50 ` Christian Brauner
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=87blmq6bw0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=christian.brauner@ubuntu.com \
--cc=fenghua.yu@intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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