Subject: Re: bug#79334: [PATCH] Don't release thread select lock unnecessarily

From: Eli Zaretskii <[email-masked]>
Date: Fri, 29 Aug 2025 18:57:33 +0300

> From: Spencer Baugh <[email-masked]>
> Date: Fri, 29 Aug 2025 11:43:21 -0400
> Cc: [email-masked], [email-masked], Dmitry Gutov <[email-masked]>
> 
> Okay, so then how about we delete this unsafe thread_select and put some thread-yield calls around
> wait_reading_process_output?

I'm not objected to not calling thread_select there, but can we have
tests that will show us the gains?

Also, I think we should fix the problems with status_notify and other
users of FOR_EACH_PROCESS before we make the change with
thread_select, because current code in status_notify is definitely
wrong, and affects the related behavior.