Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: rajesh.palani@philips.com
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: sysmips syscall
Date: Sat, 18 Nov 2000 11:59:09 +0100	[thread overview]
Message-ID: <20001118115909.D8672@bacchus.dhis.org> (raw)
In-Reply-To: <0056910008698539000002L192*@MHS>; from rajesh.palani@philips.com on Fri, Nov 17, 2000 at 07:28:50PM -0600

On Fri, Nov 17, 2000 at 07:28:50PM -0600, rajesh.palani@philips.com wrote:

>    The following lines appear in the linuxthreads/sysdeps/mips/pt-machine.h file in version
> LinuxThreads 2.1.2:
> 
> TODO: This version makes use of MIPS ISA 2 features.  It won't
>    work on ISA 1.  These machines will have to take the overhead of
>    a sysmips(MIPS_ATOMIC_SET, ...) syscall which isn't implemented
>    yet correctly.  There is however a better solution for R3000
>    uniprocessor machines possible.
> 
> My questions are:
> 1.  Is the sysmips syscall implemented correctly yet?

Yes.

> 2.  What is the better solution for R3000 uniprocessor machines?

You can base a spinlock implementation on the fact that the register k0
will be left at a value != zero after any exception, also including context
switches.

Problem: this solution breaks silently on multiproessor systems.

> 3.  Does anyone have a patch for LinuxThreads that supports MIPS ISA 1?

glibc 2.2's pthread will do that out of the box.

  Ralf

  parent reply	other threads:[~2000-11-18 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  1:28 sysmips syscall rajesh.palani
2000-11-18  1:28 ` rajesh.palani
2000-11-18 10:59 ` Ralf Baechle [this message]
2000-11-18 13:46   ` Keith Owens
2000-11-18 14:13     ` Ralf Baechle
2000-11-18 17:26     ` Alan Cox
2000-11-18 17:26       ` Alan Cox

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=20001118115909.D8672@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=rajesh.palani@philips.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