Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jay Carlson <nop@nop.com>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: kernel should not reject -mips2 ELF binaries
Date: Tue, 7 Nov 2000 03:28:02 +0100	[thread overview]
Message-ID: <20001107032802.D28567@bacchus.dhis.org> (raw)
In-Reply-To: <KEEOIBGCMINLAHMMNDJNEEDHCAAA.nop@nop.com>; from nop@nop.com on Mon, Nov 06, 2000 at 09:20:00PM -0500

On Mon, Nov 06, 2000 at 09:20:00PM -0500, Jay Carlson wrote:

> include/asm-mips/elf.h contains a macro, elf_check_arch, that decides if an
> executable is plausible to run under this kernel.  It currently accepts
> binaries flagged as MIPS1 ISA, and rejects all other ISAs.
> 
> #define elf_check_arch(hdr)						\
> ({									\
> 	int __res = 1;							\
> 	struct elfhdr *__h = (hdr);					\
> 									\
> 	if ((__h->e_machine != EM_MIPS) &&				\
> 	    (__h->e_machine != EM_MIPS_RS4_BE))				\
> 		__res = 0;						\
> 	if (__h->e_flags & EF_MIPS_ARCH)				\
> 		__res = 0;						\
> 									\
> 	__res;								\
> })
> 
> I think we should make an exception for MIPS2.  Turns out that the two Linux
> VR processor families benefit from some of the MIPS II features; most
> notably, code density is improved by eliminating load delay slots.  If I
> build executables that take advantage of this, they legitimately should be
> flagged with E_MIPS_ARCH_2 (since they won't run on my decstation).
> 
> So what's the right way to fix this?  Three things come to mind:
> 
> 1) rip out the EF_MIPS_ARCH check from elf_check_arch.

Take 1).  The problem we have is distiguishing Linux binaries from IRIX
binaries.  The code causing problems for you is a heuristic that no
longer works these days so I'll have to come up with something new.

  Ralf

  parent reply	other threads:[~2000-11-07  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07  2:20 kernel should not reject -mips2 ELF binaries Jay Carlson
2000-11-07  2:20 ` Jay Carlson
2000-11-07  2:28 ` Ralf Baechle [this message]
2000-11-07  3:00   ` Jay Carlson
2000-11-07  3:00     ` Jay Carlson

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=20001107032802.D28567@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=nop@nop.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