From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107321 invoked by alias); 14 Feb 2020 18:20:33 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 107303 invoked by uid 89); 14 Feb 2020 18:20:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-1.mimecast.com (HELO us-smtp-1.mimecast.com) (205.139.110.61) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 14 Feb 2020 18:20:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581704430; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2iaGF452mRmcW4phkrp3xE4PsJF6/c/4qgOq2rDGHB8=; b=EndfUvdFGApW+8I0D7l1fgcFFKH2Vsx99FvPknIgRzjdTWsCbl3AAnMhrzT03rWSDMXNey HfwX0xWGUfn95R84oipuZ2jZ7PjwFo84C5bTq7N6juSNOrEKg7w54TtvMzO1kXICSZcsvM Xv/IZknxitP8+w9IZ9GRdg3aadG9hNg= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-2-YpzQvUsXNWWlAPVzt9xQpw-1; Fri, 14 Feb 2020 13:20:29 -0500 Received: by mail-wm1-f70.google.com with SMTP id p2so3900408wmi.8 for ; Fri, 14 Feb 2020 10:20:28 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f909:7b00:56ee:75ff:fe8d:232b? ([2001:8a0:f909:7b00:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id f12sm8264047wmj.10.2020.02.14.10.20.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 14 Feb 2020 10:20:25 -0800 (PST) Subject: Re: [RFC 00/17] Merge event loop implementations To: Tom Tromey References: <20190224165153.5062-1-tom@tromey.com> <3ae5ab8e-c219-6510-bb54-b30c1cf2d074@redhat.com> <87v9t4qhbu.fsf@tromey.com> Cc: gdb-patches@sourceware.org From: Pedro Alves Message-ID: <9d383fa3-583d-d7bd-7398-91fcfd4438f6@redhat.com> Date: Fri, 14 Feb 2020 18:20:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <87v9t4qhbu.fsf@tromey.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg00567.txt.bz2 Hi, found this one which I never answered. On 10/4/19 11:25 PM, Tom Tromey wrote: >>>>>> "Pedro" == Pedro Alves writes: > > Tom> Another related possible to-do item is changing the ser-event code to > Tom> maintain just a single self-pipe. It seems to me that there's never a > Tom> reason to need more than one. > > Pedro> Can you clarify/expand? Are you suggesting to use one single pipe, > Pedro> and then if select/poll wakes up, go through a list of registered > Pedro> ser-events to know which one triggered? Or something else? > > It seems to me that any use of a serial event could just be replaced > with run_on_main_thread, from the threading patches, instead. I don't see how that could replace interruptible_select (and quit_serial_event). Thanks, Pedro Alves