public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: linux-ia64@vger.kernel.org
Subject: Re: dropping CONFIG_IA32_SUPPORT from ia64
Date: Thu, 25 May 2006 15:41:55 +0000	[thread overview]
Message-ID: <20060525154155.GB31604@skunkworks.cabal.ca> (raw)
In-Reply-To: <200605241438.34303.bjorn.helgaas@hp.com>

On Thu, May 25, 2006 at 08:40:48AM -0700, Luck, Tony wrote:
> > in the pre-Montecito IPF CPUs.  AFAIK, the exact same binary is even
> > used both for the Windows and Linux versions of IA32EL.
>
<snip>
> The rest of the ia32-el package is open source ... which should
> provide enough documentation on how the OS-level code interfaces
> to the instruction execution engine to allow it to be replaced.
> 

Possibly a stupid question, but I couldn't find any information in the
(afaik) only released Montecito documentation (the Optimization guide).

Has the br.ia completer been removed from the architecture? Or will
it generate a trap which can be caught and the translator invoked?

The doc only references added insns, not those removed from the arch.

Cheers,
	Kyle

  parent reply	other threads:[~2006-05-25 15:41 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 [this message]
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=20060525154155.GB31604@skunkworks.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=linux-ia64@vger.kernel.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