From: tomas@tuxteam.de
To: sbaugh@catern.com
Cc: Dmitry Gutov <dmitry@gutov.dev>,
Spencer Baugh <sbaugh@janestreet.com>,
emacs-devel@gnu.org
Subject: Re: Releasing the thread global_lock from the module API
Date: Sun, 3 Mar 2024 07:25:29 +0100 [thread overview]
Message-ID: <ZeQX2ZvCxKXNfdPW@tuxteam.de> (raw)
In-Reply-To: <87h6hojoqi.fsf@catern.com>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Sat, Mar 02, 2024 at 09:41:38PM +0000, sbaugh@catern.com wrote:
> tomas@tuxteam.de writes:
[safe suspend wrt. concurrency]
> > I don't think this is currently possible.
>
> It is currently possible: this is what thread-yield, sleep-for, and
> accept-process-output do when run from a Lisp thread. The thread pauses
> execution and other threads execute. This has worked since the
> introduction of thread support.
Thanks for the correction.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-03-03 6:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:53 Releasing the thread global_lock from the module API Spencer Baugh
2024-03-01 16:47 ` Eli Zaretskii
2024-03-01 17:34 ` Spencer Baugh
2024-03-01 18:44 ` Eli Zaretskii
2024-03-01 19:02 ` Spencer Baugh
2024-03-01 19:26 ` Eli Zaretskii
2024-03-01 19:51 ` Spencer Baugh
2024-03-01 20:42 ` Eli Zaretskii
2024-03-01 21:21 ` Spencer Baugh
2024-03-01 21:34 ` Eli Zaretskii
2024-03-01 21:56 ` Spencer Baugh
2024-03-02 6:43 ` Eli Zaretskii
2024-03-02 16:39 ` sbaugh
2024-03-02 17:02 ` Eli Zaretskii
2024-03-02 20:33 ` Spencer Baugh
2024-03-03 6:13 ` Eli Zaretskii
2024-03-03 13:19 ` sbaugh
2024-03-03 15:42 ` Dmitry Gutov
2024-03-03 15:51 ` Eli Zaretskii
2024-03-01 19:30 ` tomas
2024-03-01 23:53 ` Dmitry Gutov
2024-03-02 5:57 ` tomas
2024-03-02 15:35 ` Dmitry Gutov
2024-03-02 16:31 ` tomas
2024-03-02 21:41 ` sbaugh
2024-03-03 6:25 ` tomas [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZeQX2ZvCxKXNfdPW@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).