From: Matt Taggart <taggart@debian.org>
To: linux-ia64@vger.kernel.org, linux-mm@kvack.org,
debian-ia64@lists.debian.org
Subject: Re: dropping CONFIG_IA32_SUPPORT from ia64
Date: Thu, 25 May 2006 01:32:44 +0000 [thread overview]
Message-ID: <20060525013244.C2F5937F81@carmen.fc.hp.com> (raw)
In-Reply-To: <200605241438.34303.bjorn.helgaas@hp.com>
Bjorn Helgaas writes...
> 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.
Debian is looking at implementing "multiarch", a way to have libraries
for multiple binary targets install in the same system root.
http://wiki.debian.org/multiarch
After amd64 systems, ia64 can benefit the most from multiarch. It would
be a shame to see this not happen.
I also agree with Bjorn that the propriatary tool shouldn't be the only
way. To the Intel people on the lists that work on this, what is Intel's
position on open sourcing this technology?
Thanks,
--
Matt Taggart
taggart@debian.org
next prev parent reply other threads:[~2006-05-25 1: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 [this message]
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=20060525013244.C2F5937F81@carmen.fc.hp.com \
--to=taggart@debian.org \
--cc=debian-ia64@lists.debian.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.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