From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>, Jens Axboe <axboe@suse.de>
Cc: hugh@veritas.com, linux-ia64@vger.kernel.org,
a.p.zijlstra@chello.nl, lee.schermerhorn@hp.com,
nickpiggin@yahoo.com.au, linux-mm@kvack.org, ak@suse.de,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [5/5] move_pages: 32bit support (i386,x86_64 and ia64)
Date: Wed, 24 May 2006 20:32:53 +0000 [thread overview]
Message-ID: <20060524133253.23fe19a2.akpm@osdl.org> (raw)
In-Reply-To: <20060523174410.10156.43268.sendpatchset@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@sgi.com> wrote:
>
> sys_move_pages() support for 32bit (i386 plus ia64 and x86_64 compat layers)
>
> Add support for move_pages() on i386 and also add the
> compat functions necessary to run 32 bit binaries on x86_64 and ia64.
>
> Add compat_sys_move_pages to both the x86_64 and the ia64 32bit binary
> layer. Note that both are not up to date so I added the missing pieces.
> Not sure if this is done the right way.
>
> This probably needs some fixups:
>
> 1. What about sys_vmsplice on x86_64?
>
> 2. There is a whole range of syscalls missing for ia64 that I basically
> interpolated from elsewhere.
I dropped the ia64 bits - looks like that's all on death row anyway.
The omission of sys_vmsplice() from the x86 syscall table does appear to
be, umm, a glaring omission. Jens, what's up?
next prev parent reply other threads:[~2006-05-24 20:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 17:43 [0/5] sys_move_pages() updates Christoph Lameter
2006-05-23 17:43 ` [1/5] follow_page: do not put_page if FOLL_GET not specified Christoph Lameter
2006-05-23 18:29 ` Peter Zijlstra
2006-05-23 17:43 ` [2/5] extract common code to have_task_perm() Christoph Lameter
2006-05-23 17:43 ` [3/5] move_pages: lots of fixups Christoph Lameter
2006-05-23 17:44 ` [4/5] move_pages: x86_64 support Christoph Lameter
2006-05-23 17:44 ` [5/5] move_pages: 32bit support (i386,x86_64 and ia64) Christoph Lameter
2006-05-24 18:45 ` Luck, Tony
2006-05-24 18:58 ` Andrew Morton
2006-05-24 19:01 ` Christoph Lameter
2006-05-24 20:38 ` dropping CONFIG_IA32_SUPPORT from ia64 Bjorn Helgaas
2006-05-24 21:23 ` Luck, Tony
2006-05-24 21:37 ` Jeff Hanson
2006-05-24 21:45 ` Peter Chubb
2006-05-24 22:30 ` Rich Altmaier
2006-05-25 0:05 ` Matthew Wilcox
2006-05-25 0:56 ` Luck, Tony
2006-05-25 1:07 ` Kyle McMartin
2006-05-25 1:32 ` Matt Taggart
2006-05-25 3:30 ` Andi Kleen
2006-05-25 15:09 ` Luck, Tony
2006-05-25 15:16 ` Luck, Tony
2006-05-25 15:27 ` David Mosberger-Tang
2006-05-25 15:40 ` Luck, Tony
2006-05-25 15:41 ` Kyle McMartin
2006-05-25 17:22 ` Luck, Tony
2006-05-26 5:59 ` dann frazier
2006-05-26 7:11 ` Jes Sorensen
2006-05-26 8:59 ` Andreas Schwab
2006-05-26 13:42 ` Christoph Hellwig
2006-05-26 18:25 ` Luck, Tony
2006-05-24 19:18 ` [5/5] move_pages: 32bit support (i386,x86_64 and ia64) Luck, Tony
2006-05-24 20:32 ` Andrew Morton [this message]
2006-05-24 20:33 ` Jens Axboe
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=20060524133253.23fe19a2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=axboe@suse.de \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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