Re: Some experience with the igc branch

[Eli Zaretskii <eliz@gnu.org>]

> From: Helmut Eller <eller.helmut@gmail.com>
> Cc: gerd.moellmann@gmail.com,  pipcet@protonmail.com,  ofv@wanadoo.es,
>   emacs-devel@gnu.org,  acorallo@gnu.org
> Date: Wed, 25 Dec 2024 21:44:21 +0100
> 
> On Wed, Dec 25 2024, Eli Zaretskii wrote:
> 
> > Which means we should try talking to the MPS folks so that they
> > provide us with the means of blocking some signals while the lock is
> > held.  Like some callback MPS would call when it takes the lock and
> > another one when it releases the lock.
> 
> Your position is that blocking SIGPROF while MPS holds the lock is
> the correct thing to do, right?

Yes, I think so.  (If you disagree, please tell why, and let's discuss
that.)  It is certainly a relatively simple thing to do.

It is also possible for MPS to somehow manage an attempt to take the
lock which is already held in a smarter way, by stopping the code
which does that until MPS releases the lock.  For example, MPS could
define a protocol for such situations not unlike the GIL protocol we
use for Lisp threads.  But that's much more complex, and I don't
necessarily expect the MPS folks to go to such lengths.