From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Some experience with the igc branch Date: Thu, 26 Dec 2024 08:29:30 +0200 Message-ID: <86ttaryn1x.fsf@gnu.org> References: <87o713wwsi.fsf@telefonica.net> <87pllicrpi.fsf@protonmail.com> <864j2u442i.fsf@gnu.org> <87ldw6as5f.fsf@protonmail.com> <86o7112rnq.fsf@gnu.org> <867c7p2nz4.fsf@gnu.org> <861pxx2lh7.fsf@gnu.org> <86ldw40xbo.fsf@gnu.org> <86a5cj2a0e.fsf@gnu.org> <867c7n28sf.fsf@gnu.org> <877c7n962e.fsf@gmail.com> <8634ib24gp.fsf@gnu.org> <875xn75w7u.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23377"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, pipcet@protonmail.com, ofv@wanadoo.es, emacs-devel@gnu.org, acorallo@gnu.org To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 26 07:30:17 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tQhNw-0005v8-FG for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Dec 2024 07:30:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tQhNK-0000Mx-6g; Thu, 26 Dec 2024 01:29:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tQhNG-0000Mk-Td for emacs-devel@gnu.org; Thu, 26 Dec 2024 01:29:35 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tQhNF-0005hi-0a; Thu, 26 Dec 2024 01:29:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=wbTPoIvyj25yepIfaAOS2dTMFqKUNZ7tD419BlOOcGY=; b=DDh5j2rC/mcv gge5yEzoeyMU9DWkdh0g/6rdKPCESIFBU1qASoSpU3yiN1nMWTKE1AtZzaFP818LybWqfXADEpXpt ed7xEMw7+5LTSDAdbu+bxdvS7CuMLkZod54bgw97syHaR78KoD/AZFUfF7Utu/+vlFGa3LW8e211V k0whk4+I0QAy/aqp7QpNa6KVK7Lk4v9uXtHP7b8/i8BT1dED3XCELRbPagzDKhJe/OgPtBgZNnIT3 JU5IkGIdhXLk8K1xFZIo+8sFoozM7XGr39/wHzz0hXUvdS+b0tAKBGc29XnD7IL1Jh7dMzwCYzMH1 3nHDG7g5ejqMFWmEPYxUDQ==; In-Reply-To: <875xn75w7u.fsf@gmail.com> (message from Helmut Eller on Wed, 25 Dec 2024 21:44:21 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327134 Archived-At: > From: Helmut Eller > 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.