Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, Florian Lohoff <flo@rfc822.org>,
	linux@cthulhu.engr.sgi.com
Subject: Re: Decstation 5000/150 2.3.21 Boot successs
Date: Fri, 7 Jan 2000 00:54:20 +0100	[thread overview]
Message-ID: <20000107005420.C17537@uni-koblenz.de> (raw)
In-Reply-To: <00ef01bf5859$6d11f410$0ceca8c0@satanas.mips.com>

On Thu, Jan 06, 2000 at 04:19:27PM +0100, Kevin D. Kissell wrote:

> >If that's desired, how about providing a syscall which allows to manipulate
> >this and possibly other bits?
> 
> I very much prefer the idea of having exec() to the right thing, so
> that 32/32 fpr and o32 ABI programs can be mixed and matched
> as appropriate - assuming, of course, that there's sufficient information
> in the binary header to do the job!  In practical terms, given that
> Linux is a multiuser and multitasking system, a syscall that throws
> some sort of global switch could only be safely invoked once
> at boot time, and as such offers little advantage over hardwired
> kernel code.

I was suggesting such a syscall because embedded people have asked me about
making the 32/32 fpr model available to `normal' o32 code.  N32 won't work
for them for practical reasons (linker tooo buggy) and 64-bit ABI is
unacceptable for size / tlb / cache reasons.

For the general case you're of course right, exec() should do the right
thing.  And modulo the bug we're discussing here the 32-bit kernel already
does the right thing to handle the general case.

  Ralf

  parent reply	other threads:[~2000-01-07  0:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 15:19 Decstation 5000/150 2.3.21 Boot successs Kevin D. Kissell
2000-01-06 15:19 ` Kevin D. Kissell
2000-01-06 23:54 ` Ralf Baechle [this message]
2000-01-07  1:50   ` William J. Earl
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06  9:12 Kevin D. Kissell
2000-01-06  9:12 ` Kevin D. Kissell
2000-01-06 14:26 ` Ralf Baechle
2000-01-06 19:10   ` William J. Earl
2000-01-06 18:57 ` William J. Earl
2000-01-06 18:57   ` William J. Earl
2000-01-07 19:09   ` Harald Koerfgen
2000-01-07 23:29     ` Ralf Baechle
2000-01-08  1:30     ` William J. Earl
2000-01-05 21:18 Florian Lohoff

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=20000107005420.C17537@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=flo@rfc822.org \
    --cc=kevink@mips.com \
    --cc=linux@cthulhu.engr.sgi.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