From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Cooperative POSIX threads?
Date: 21 Oct 2002 17:46:25 +0200 [thread overview]
Message-ID: <87u1jfvlpq.fsf@zagadka.ping.de> (raw)
Hi,
I noticed that signal delivery does not really work when using coop
threads together with the LinuxThreads compatability workaround (i.e,
when configured --with-threads=coop and --enable-linuxthreads)
While pondering what to do, I thought about the following:
Let's make another thread suport option, "coop-pthreads" that will use
pthreads for implementing threads but will rig it so that all threads
that use Guile are executing cooperatively.
There will be new C functions that will bring a thread into Guile
land, and make it leave again. While a thread is in Guile land, it
can call Guile functions, etc. When it is outside, it can't. Threads
created by Guile itself will start in Guile land. scm_boot_guile and
scm_init_guile will do the right thing, but I'm not yure yet what that
is for scm_init_guile.
We will need these Guile entering and leaving functions anyway when we
want external threads to use Guile since we need to know about the
relevant stack segments. Those functions can take care that only one
thread is in Guile land at the same time.
Later the coop restriction can be lifted, when Guile itself can
survive this.
Thoughts?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-10-21 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:46 Marius Vollmer [this message]
2002-10-21 18:01 ` Cooperative POSIX threads? Mikael Djurfeldt
2002-10-21 18:47 ` Marius Vollmer
2002-10-21 19:52 ` Mikael Djurfeldt
2002-10-21 20:39 ` Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u1jfvlpq.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).