From: Andi Kleen <ak@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Christoph Lameter <clameter@sgi.com>,
akpm@osdl.org, Hugh Dickins <hugh@veritas.com>,
linux-ia64@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
debian-ia64@lists.debian.org
Subject: Re: dropping CONFIG_IA32_SUPPORT from ia64
Date: Thu, 25 May 2006 03:30:59 +0000 [thread overview]
Message-ID: <200605250531.00108.ak@suse.de> (raw)
In-Reply-To: <200605241438.34303.bjorn.helgaas@hp.com>
> I'm a bit worried about this. As I understand it, the Intel
> software emulator is not open-source. There may be distros
> like Debian and customer environments where that's not a viable
> alternative.
>
> If we remove CONFIG_IA32_SUPPORT, every ia64 box will require
> the Intel emulator (or QEMU or some other ill-defined solution)
> in order to run ia32 code, even though every processor in the
> field today supports ia32 in hardware.
>
> It doesn't feel right to me to remove functionality from machines
> in the field and offer only a proprietary alternative.
You could just freeze the code down to "security fixes only".
This means new system calls wouldn't need to be added and most programs
fallback if they don't see the latest and great syscalls anyways.
On the other hand it is usually not very hard to add new syscalls
and most of the other code is shared now anyways.
-Andi
next prev parent reply other threads:[~2006-05-25 3:30 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 [this message]
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=200605250531.00108.ak@suse.de \
--to=ak@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=clameter@sgi.com \
--cc=debian-ia64@lists.debian.org \
--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