Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Joe deBlaquiere <jadb@redhat.com>,
	Florian Lohoff <flo@rfc822.org>,
	linux-mips@oss.sgi.com
Subject: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call
Date: Sat, 27 Jan 2001 11:42:11 -0800	[thread overview]
Message-ID: <20010127114211.L867@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010127082028.29150B-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Sat, Jan 27, 2001 at 08:28:05AM +0100

On Sat, Jan 27, 2001 at 08:28:05AM +0100, Maciej W. Rozycki wrote:

> > Afaik the only user of MIPS_ATOMIC_SET ever running on Linux/MIPS is the
> > Linuxthreads code you wrote, so no.  Aside of that the semantics of this
> > syscall were defined by older MIPS operating systems such as Risc/OS and
> > I think we should follow their example.
> 
>  I still haven't seen a definite spec for the call.

Sorry, the specs is code and docs I have access to here inside SGI and which
I cannot pass on ...

>  Since you suggest the Linuxthreads code is the only user of the code
> (also remember the _test_and_set library function as specified by the ABI),
> we might abandon MIPS_ATOMIC_SET and write a _test_and_set syscall
> instead.  No compatibility issues would be involved and the definition is
> clear in the ABI (the library function would become a simple wrapper). 

We have an IRIX 5 emulation and if I remember right for IRIX 5
MIPS_ATOMIC_SET is still supported, so we need to also.  So I fear we'll
have to keep sysmips.  Which still doesn't mean we should come up with
something better.

>  I'm still uncertain if wasting a syscall number is that great idea, but
> we would be free from any compatibility problems.  And yes, I still think
> an ll/sc emulation could be done independently anyway. 

  Ralf

  reply	other threads:[~2001-01-28  2:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 15:30 OOps - very obscure Florian Lohoff
2001-01-24 15:59 ` Florian Lohoff
2001-01-24 16:22   ` Florian Lohoff
2001-01-24 21:18   ` Keith Owens
2001-01-25 12:43   ` Florian Lohoff
2001-01-25 18:59     ` Jun Sun
2001-01-25 19:22       ` Florian Lohoff
2001-01-25 15:55   ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Florian Lohoff
2001-01-25 15:55     ` Florian Lohoff
2001-01-25 16:34     ` Origin 200 crash nick
2001-01-25 18:28     ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Joe deBlaquiere
2001-01-25 19:35       ` Joe deBlaquiere
2001-01-25 22:19         ` Ralf Baechle
2001-01-26  0:53           ` Joe deBlaquiere
2001-01-26 10:21             ` Maciej W. Rozycki
2001-01-26 15:41               ` Joe deBlaquiere
2001-01-26 21:16                 ` Ralf Baechle
2001-01-27  7:20                 ` Maciej W. Rozycki
2001-01-26 21:15               ` Ralf Baechle
2001-01-27  7:28                 ` Maciej W. Rozycki
2001-01-27 19:42                   ` Ralf Baechle [this message]
2001-01-29 15:03                     ` Maciej W. Rozycki
2001-01-26 20:01             ` Jun Sun
2001-01-26 20:38               ` Joe deBlaquiere
2001-01-26 21:02                 ` Jun Sun
2001-04-04 22:13           ` Florian Lohoff
2001-02-19 13:11     ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Wichert Akkerman
2001-02-19 19:52       ` newbie question Can Altineller
2001-02-20  7:06         ` David Jez
2001-02-20 20:26           ` Mike McDonald
2001-02-20 20:30             ` nick
2001-02-20 20:53             ` Ralf Baechle
2001-02-20 20:41       ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Ralf Baechle

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=20010127114211.L867@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=flo@rfc822.org \
    --cc=jadb@redhat.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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