From: Arnd Bergmann <arnd@arndb.de>
To: Narendra Prasad Madanapalli <narendramind@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
torvalds@osdl.org, linux-api@vger.kernel.org,
mtk.manpages@googlemail.com
Subject: Re: [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls to provide FSIZE limits > 2^32-1
Date: Fri, 30 Jan 2009 19:04:51 +0100 [thread overview]
Message-ID: <200901301904.52328.arnd@arndb.de> (raw)
In-Reply-To: <85e5430e0901300957x64951d6at2a79c5cb1ee88e97@mail.gmail.com>
On Friday 30 January 2009, Narendra Prasad Madanapalli wrote:
> Can you provide me more information on how to port these system calls
> to 32-on-64 kernel.
Your interface has compatible calling conventions between 32 and 64
bit user programs, so for x86, all you need to do is to add them to
arch/x86/ia32/ia32entry.S in the same way as you did for
arch/x86/kernel/syscall_table_32.S.
For the other architectures, the respective maintainers will take
care of this if your patch gets accepted. Unfortunately, each
architecture has a different way of adding the compat system
calls.
Arnd <><
next prev parent reply other threads:[~2009-01-30 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 17:59 [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls to provide FSIZE limits > 2^32-1 narendramind
2009-01-26 19:04 ` Arnd Bergmann
2009-01-27 0:46 ` Michael Kerrisk
2009-01-30 17:57 ` Narendra Prasad Madanapalli
2009-01-30 18:04 ` Arnd Bergmann [this message]
2009-01-26 19:23 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 17:53 narendramind
2009-01-23 17:49 narendramind
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=200901301904.52328.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=narendramind@gmail.com \
--cc=torvalds@osdl.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