From: "H. Peter Anvin" <hpa@zytor.com>
To: sukadev@us.ibm.com
Cc: Andrew Morton <akpm@osdl.org>,
clg@fr.ibm.com, serue@us.ibm.com,
"David C. Hansen" <haveblue@us.ibm.com>,
Pavel Emelyanov <xemul@openvz.org>,
Containers <containers@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] clone64() and unshare64() system calls
Date: Wed, 09 Apr 2008 18:10:57 -0700 [thread overview]
Message-ID: <47FD6921.6090408@zytor.com> (raw)
In-Reply-To: <20080410010717.GA28477@us.ibm.com>
sukadev@us.ibm.com wrote:
>>
>> If you're going to make it a 64-bit pass it in as a 64-bit number, instead
>> of breaking it into two numbers.
>
> Maybe I am missing your point. The glibc interface could take a 64bit
> parameter, but don't we need to pass 32-bit values into the system call
> on 32 bit systems ?
Not as such, no. The ABI handles that. To make the ABI clean on some
architectures, it's good to consider a 64-bit value only in positions
where they map to an even:odd register pair once slotted in.
> Yes, this was discussed before in the context of Pavel Emelyanov's patch
>
> http://lkml.org/lkml/2008/1/16/109
>
> along with sys_indirect(). While there was no consensus, it looked like
> adding a new system call was better than open ended interfaces.
That's not really an open-ended interface, it's just an expandable bitmap.
-hpa
next prev parent reply other threads:[~2008-04-10 1:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 22:26 [PATCH 0/3] clone64() and unshare64() system calls sukadev
2008-04-09 22:32 ` [PATCH 1/3] change clone_flags type to u64 sukadev
2008-04-10 8:25 ` Andi Kleen
2008-04-10 12:25 ` Cedric Le Goater
2008-04-10 12:52 ` Andi Kleen
2008-04-10 13:11 ` Kirill Korotaev
2008-04-10 13:23 ` Cedric Le Goater
2008-04-10 13:18 ` Cedric Le Goater
2008-04-10 17:14 ` Serge E. Hallyn
2008-04-10 22:13 ` Daniel Hokka Zakrisson
2008-04-10 22:49 ` Serge E. Hallyn
2008-04-11 8:45 ` Daniel Hokka Zakrisson
2008-04-09 22:34 ` [PATCH 2/3] add do_unshare() sukadev
2008-04-09 22:34 ` [PATCH 3/3] add the clone64() and unshare64() syscalls sukadev
2008-04-09 23:07 ` Jakub Jelinek
2008-04-10 2:15 ` sukadev
2008-04-10 3:40 ` H. Peter Anvin
2008-04-10 0:00 ` [PATCH 0/3] clone64() and unshare64() system calls H. Peter Anvin
2008-04-10 1:07 ` sukadev
2008-04-10 1:10 ` H. Peter Anvin [this message]
2008-04-10 2:38 ` sukadev
2008-04-10 2:43 ` Paul Menage
2008-04-10 18:26 ` sukadev
2008-04-10 18:31 ` H. Peter Anvin
2008-04-10 12:33 ` Cedric Le Goater
2008-04-10 16:00 ` H. Peter Anvin
2008-04-10 6:48 ` Cedric Le Goater
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=47FD6921.6090408@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=sukadev@us.ibm.com \
--cc=xemul@openvz.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