From: Jun Sun <jsun@mvista.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: userspace spinlocks
Date: Mon, 30 Oct 2000 09:51:06 -0800 [thread overview]
Message-ID: <39FDB50A.4919D84E@mvista.com> (raw)
In-Reply-To: 20001030151736.C2687@paradigm.rfc822.org
Florian Lohoff wrote:
>
> OTOH - Where are they normally implemented ? libc ? macro ?
As far I know, they ether use atomic instructions such as ll/sc or use
kernel trap to emulate atomic operations. I am not sure if other means
are possible because userland cannot disable interrupts or prevent
context switch.
> 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.
Jun
next prev parent reply other threads:[~2000-10-30 17:50 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 [this message]
2000-10-31 20:14 ` Ralf Baechle
2000-10-31 22:01 ` Jun Sun
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=39FDB50A.4919D84E@mvista.com \
--to=jsun@mvista.com \
--cc=flo@rfc822.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox