All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: Build failure for R3000 DECstation
Date: Wed, 15 Nov 2000 00:41:22 +0100	[thread overview]
Message-ID: <20001115004122.G927@bacchus.dhis.org> (raw)
In-Reply-To: <XFMail.001114223017.Harald.Koerfgen@home.ivm.de>; from Harald.Koerfgen@home.ivm.de on Tue, Nov 14, 2000 at 10:30:17PM +0100

On Tue, Nov 14, 2000 at 10:30:17PM +0100, Harald Koerfgen wrote:

> > Obviously none of them seemed to care so now I'm doing the quick fix.
> > Frankly, a syscall which shouldn't be used doesn't deserve more attention ...
> 
> Well, it seems as if there are people with a different opinion. Fresh from the
> glibc CVS (libc/sysdeps/unix/sysv/linux/mips/sys/tas.h):

I know.  Otherwise I'd have plain killed this syscall rsn.

> Personally I like this more than a kernel ll/sc emulation. A syscall is likely
> to be faster than at least two illegal instruction exceptions. If you're
> concerned about binary compatibilty, the syscall should work on ISA>=2 CPUs as
> well.

The idea is to punish the least widespread architecture and this are the
non-ll/sc CPUs.  Just like Linux is no longer performing optimally on x86.

In any case, for uniprocessor non-ll/sc machines there is also a better
solution availble with no syscalls at all.  It's easy to implement, just
use the fact that any exception will change the values of k0/k1.  That of
course breaks silently on SMP.

glibc 2.2 calls this sysmips(). very often so optimizing them is fairly
important ...

  Ralf

  reply	other threads:[~2000-11-14 23:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-12 20:00 Build failure for R3000 DECstation Jan-Benedict Glaw
2000-11-13  9:47 ` Ralf Baechle
2000-11-14 21:30   ` Harald Koerfgen
2000-11-14 23:41     ` Ralf Baechle [this message]
2000-11-15  0:58       ` Maciej W. Rozycki
2000-11-15  1:43         ` Ralf Baechle
2000-11-15  3:13           ` Jun Sun
2000-11-15  3:16             ` Ralf Baechle
2000-11-15 11:21             ` Maciej W. Rozycki
2000-11-15 19:46             ` Harald Koerfgen
2000-11-15 20:17               ` Maciej W. Rozycki
2000-11-15 20:21                 ` Jun Sun
2000-11-16 13:23                   ` Maciej W. Rozycki
2000-11-15 20:17               ` Jun Sun
2000-11-15 20:31                 ` Maciej W. Rozycki
2000-11-15 11:18           ` Maciej W. Rozycki
2000-11-16  1:27             ` Ralf Baechle
2000-11-16 13:41               ` Maciej W. Rozycki
2000-11-15 19:46       ` Harald Koerfgen
2000-11-13 21:03 ` Harald Koerfgen

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=20001115004122.G927@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=Harald.Koerfgen@home.ivm.de \
    --cc=linux-mips@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.