From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@oss.sgi.com
Subject: Re: userspace spinlocks
Date: Tue, 31 Oct 2000 14:01:49 -0800 [thread overview]
Message-ID: <39FF414D.6B0A553C@mvista.com> (raw)
In-Reply-To: 20001031211431.C28909@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Mon, Oct 30, 2000 at 09:51:06AM -0800, Jun Sun wrote:
>
> > > Could
> > > there be a runtime linking thing with a cpu detection wether we
> > > have ll/sc or not ?
> >
> > This is a wonderful idea. It should incorporate into future MIPS CPU
> > support structure.
>
> But what is the better alternative? Emulating ll/sc is a generic facility.
> Aside of making that more efficient the only idea I have is putting entire
> atomic operations into the kernel such that the standard case should result
> in at most one exception to be handled in the kernel.
>
When I was playing with NEC Vr4111 (a MIPS III cpu but without ll/sc), I
notice the following comment in
glibc/linuxthreads/sysdeps/mips/pt-machine.h file (Is that Ralf's
comment?) :
"
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. */
"
I remembered I found a patch which actually uses mips syscalls. For
some reasons, it did not work in the end.
BTW, I didn't know the kernel already has ll/sc emulation. That seems
to be necessary, even just for the binary compability sake.
Jun
next prev parent reply other threads:[~2000-10-31 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 14:17 userspace spinlocks Florian Lohoff
2000-10-30 17:51 ` Jun Sun
2000-10-31 20:14 ` Ralf Baechle
2000-10-31 22:01 ` Jun Sun [this message]
2000-11-01 6:50 ` Mike Klar
2000-11-01 6:50 ` Mike Klar
2000-11-01 13:36 ` Ralf Baechle
2000-11-01 16:40 ` Mike Klar
2000-11-01 16:40 ` Mike Klar
2000-11-01 9:09 ` Florian Lohoff
2000-10-31 18:22 ` 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=39FF414D.6B0A553C@mvista.com \
--to=jsun@mvista.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox