Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Daniel Barlow <dan_b@us...> - 2002-11-24 02:36:45
Update of /cvsroot/sbcl/sbcl
In directory sc8-pr-cvs1:/tmp/cvs-serv14687
_Experimental_ branch for Linux native thread support.
From time to time the code checked in on this branch may compile,
and possibly even run. This is by no means guaranteed
New files threads.txt and TODO.dan indicate general approach and
outstanding short-term goals to get there
SYMBOL primitive object gains a tls-offset slot
LDT hackery code at os_init time (x86 linux only) sets up a
thread-local storage area using a segment selector, and makes
%gs point to it
symbol-value vop checks thread-local storage area at tls-offset
before referring to global value slot
--- NEW FILE: threads.txt ---
Some notes about the threading implementation
1) dynamic bindings
dynamic symbol bindings ("special variables") are per-thread. We
implement this using a thread-local storage area which is pointed to
(on x86) using the GS segment register.
Every symbol gets a new slot tls-index, which is an index into a
per-thread vector which contains thread-local values. The symbol
retains its global value slot as well, which is used if the
thread-local value in the current thread is set to the magic "unbound"
marker. The thread-local vector is initially filled with unbound
markers. When new threads are collected the current thread's tlv is
duplicated for the new one.
The zeroth entry in the TLV is not used: always set to unbound-marker.
New symbols get a tls-offset of 0, so that works out
When a symbol is first bound, it is assigned the next available offset
in the thread-local variable vector. Also we push it onto the binding
stack _twice_: first with the previous real (global) binding, then
with an unbound-marker.
Symbol value lookup looks first in the TLV at the sppropriate offset,
then at the global value if the TLV offset is unbound.
When a symbol is unbound, we check
1) if the tlv value is unbound, we assign the new value to the
symbol's global value slot
2) if the new value is unbound, we assign the new value to the
tlv value, then unbind again
3) otherwise we assign the new value to the tlv value
--- NEW FILE: TODO.dan ---
1) fill tlv with unbound markers
2) grow tlv when full
3) implement bind vop
4) implement unbind vop
5) implement set-symbol-value
6) figure out all the places using fast variants of symbol values
7) work out what to do with static symbols, some of which
may have bindings that are expected to be visible across thread switches
8) reintroduce per-thread stacks and stuff from the last time we did