From: Jakub Jermar <jj@comberg.cz>
To: 9fans@cse.psu.edu
Subject: [9fans] Kernel question: i386 test-and-set problem
Date: Mon, 10 Jul 2000 09:57:05 +0000 [thread overview]
Message-ID: <8kasmg$2k9e$1@news.vol.cz> (raw)
Hi all,
I've just been studying the 9 kernel and found something very weird.
In /sys/src/9/pc/l.s, there is an assembly function called tas() that should
provide its callers with an atomic test-and-set operation. This function is
called, for instance, by lock() from taslock.c.
The weird thing is that it looks as though this function only exchanged %eax
and (%ebx) by XCHG instruction which is NOT atomic. The C source looks
satisfied with it (I have no opportunity to try it, because I am not running
Plan 9 - yet :-).
By further searching, I found (in /sys/src/lithread/386cas.s... or
something) a routine called cas(). This routine uses the proper 386 atomic
instruction CMPXCHG.
Well, what's going on? I'd expect all those C functions to call cas()
instead of tas(). Mys second question is why cas() is not the only tas()
(test-end-set) within the 386 part of the kernel. My last question is why
the cas() is outside the kernel tree.
Regards,
Jakub Jermar
next reply other threads:[~2000-07-10 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 9:57 Jakub Jermar [this message]
2000-07-10 12:40 Russ Cox
2000-07-11 8:51 ` Jakub Jermar
2000-07-10 16:21 miller
2000-07-20 2:03 jmk
2000-07-20 13:54 miller
2000-07-20 17:09 presotto
2000-07-21 9:10 miller
2000-07-21 13:15 presotto
2000-07-23 14:41 miller
2000-07-31 17:26 presotto
2000-08-02 8:32 miller
2000-08-02 13:20 presotto
2000-08-02 14:51 miller
2000-08-02 15:43 jmk
2000-08-02 16:24 presotto
2000-08-03 9:56 miller
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='8kasmg$2k9e$1@news.vol.cz' \
--to=jj@comberg.cz \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).