From: Andrew Morton <akpm@osdl.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: clameter@sgi.com, 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 18:58:20 +0000 [thread overview]
Message-ID: <20060524115820.633708cf.akpm@osdl.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0693FC5B@scsmsx401.amr.corp.intel.com>
"Luck, Tony" <tony.luck@intel.com> wrote:
>
> > 2. There is a whole range of syscalls missing for ia64 that I basically
> > interpolated from elsewhere.
>
> I've been thinking of dropping CONFIG_IA32_SUPPORT completely from ia64.
> I've heard no complaints that new syscalls are not being added to the
> ia32 compat side ... which is an indication that people are not
> actively using this. Some OSDs have been building with this
> turned off for a while now (perhaps in preparation for "Montecito"
> which no longer has h/w support for the x86 instruction set, or
> perhaps because it represnts a huge block of lightly/barely tested
> code that will have its share of support issues).
>
> I suppose I should do this by adding an entry to
> Documentation/feature-removal-schedule.txt
I don't think people actively look in there. You'd also need to do
something like mark it CONFIG_BROKEN, which will wake people up and might
make them go look to see what happened. Updating the now-BROKEN help text
would make that nice and easy for them.
> Any thoughts on the timeline for this? Is Dec 31, 2006 too soon?
> (or not soon enough!?).
You'd know better than we..
next prev parent reply other threads:[~2006-05-24 18:58 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 [this message]
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
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=20060524115820.633708cf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@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 \
--cc=tony.luck@intel.com \
/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