From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: igc, macOS avoiding signals Date: Mon, 30 Dec 2024 20:03:23 +0000 Message-ID: <87a5cdx7lb.fsf@protonmail.com> References: <799DDBC5-2C14-4476-B1E0-7BA2FE9E7901@toadstyle.org> <8734i5o6wc.fsf@gmail.com> <87cyh9mpn5.fsf@gmail.com> <874j2l1hei.fsf@protonmail.com> <874j2lmd37.fsf@gmail.com> <874j2lyz1c.fsf@protonmail.com> <877c7hyoxd.fsf@gmail.com> Reply-To: Pip Cet Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32727"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?utf-8?Q?Gerd_M=C3=B6llmann?= , Eli Zaretskii , spd@toadstyle.org, emacs-devel@gnu.org To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 31 04:22:00 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 1tSSpU-0008JL-6T for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Dec 2024 04:22:00 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSSof-00055c-4N; Mon, 30 Dec 2024 22:21:09 -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 1tSLzD-00055R-Ic for emacs-devel@gnu.org; Mon, 30 Dec 2024 15:03:40 -0500 Original-Received: from mail-4322.protonmail.ch ([185.70.43.22]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSLzB-0005w5-6b; Mon, 30 Dec 2024 15:03:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1735589008; x=1735848208; bh=wdQsMKPe7F75iqtekZ0672w7xHGBr8h5IyiAdC7thZU=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=efVVQDKcKO8pGPECYzlOtp2V0FJfrvHjznZnPXP5baL5c6yn9/zNpeQsQhVkdYQaq TU7V8HT6GvjzmZfeHhaPD6GKzz2wJ44D7vx7kzlJ6q4H9nVmJojGEDLsWezcWeC4nH O8sDqx+EAirtKcJohRyox3shX/oKt4Du8+gQZUxFgnCY1K10JbsYsB2AYUmvlxjR4q xO2Iv+60oiVfuy6NPCCpkfz9BFLpq0aiVADkrr+tN+NTMRBANUIJPI2IKN6SGqtyqC pOFPzif3qA5K/KxWv3jP8m7celPonz7cGl1DCBaPo76ehwpY+6mvg1vo1JdILYitcJ srB5Q+BazeQzg== In-Reply-To: <877c7hyoxd.fsf@gmail.com> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: b3962486409fd694b31d2b26adcceefe3b978bf4 Received-SPF: pass client-ip=185.70.43.22; envelope-from=pipcet@protonmail.com; helo=mail-4322.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 30 Dec 2024 22:21:01 -0500 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:327472 Archived-At: "Helmut Eller" writes: > On Mon, Dec 30 2024, Pip Cet wrote: > >> IMHO, we now have three solutions that are still in the running (my >> order of preference): >> >> 1. keep the current code and special-case some signals which are needed >> for user responsiveness >> 2. use the signal serialization thread you proposed >> 3. use an allocation thread, but keep SIGSEGV on the main thread > > I think this is missing: > > 4. add callbacks to ArenaEnter/ArenaLeave to block/unblock signals Everything that requires MPS modifications for all users (rather than having a few users benefit from them, if they choose to run a modified MPS) isn't on my list. > Perhaps add 5. (or make it a variant of 1) > > 5. special-case some performance critical handlers and simplify all > others so that they are obviously harmless. That's a "rewrite Emacs signal handling" project, not a "add MPS to Emacs" project. That said, I'm all for it. The MPS part is definitely subsumed by (1). > The SIGIO handler is an example for a harmless signal handler. > handle_alarm_signal seems harmless too. It needs low latency, but not high throughput, AFAIK. I consider that part of "performance". > handle_interrupt_signal is definitely not harmless, but may not be > preformance critical. That's meant to do unsafe things on some systems, IIUC. > So far SIGPROF seems to be the only performance cortical handler. I wouldn't count out SIGALRM. Pip