From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Cs/cAbF1Y2SPuAsAWB0awg (envelope-from ) for ; Tue, 16 May 2023 08:23:13 -0400 Received: by simark.ca (Postfix, from userid 112) id EB2361E11E; Tue, 16 May 2023 08:23:12 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=lists.lttng.org header.i=@lists.lttng.org header.a=rsa-sha256 header.s=default header.b=f7iqF9Vc; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id CA6E51E111 for ; Tue, 16 May 2023 08:23:11 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1684239791; bh=Fu3GtSx9Mi+OWbBBTDMdWBa7lWvI0LuFSwA/2NQ7XwY=; h=Date:To:References:In-Reply-To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=f7iqF9VcnTdbWZ9pnW3VIoWBMvIXsX+vON6DlCOdMOrQEdGqTNQfkn6GDENAehkcV d3B0icY1xsQ4lUAjNPV4HU6XSJxDUurU+FVInjAWUZ7Rf/Jx65OXtdSvf82EV8o+fZ Gzd1w1hii/ywXLuD5r5ahmFQshJ2FL8jk/Zpz09HmnZI82GoXbV5lW2kgVcZB1nJsm K5EqAXADjhaFL82Bf4pnaqORvrDMvwObTWYzdDFuSpk+kAVnZX50GPXK80bbOSBuIu DnPLQZU9RqQDHfyAs9qmxrJ04MGx00hM3tMo2w+ymOz9Cj8Waa1xXMFwPAptAVi+9X Htoee1jN+JnHQ== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4QLFkl20Gtz1F82; Tue, 16 May 2023 08:23:11 -0400 (EDT) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lists.lttng.org (Postfix) with ESMTPS id 4QLFkj4MRdz1F7s for ; Tue, 16 May 2023 08:23:09 -0400 (EDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7AD5563961; Tue, 16 May 2023 12:16:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D9628C4339B; Tue, 16 May 2023 12:16:27 +0000 (UTC) Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 73CD0CE1432; Tue, 16 May 2023 05:16:27 -0700 (PDT) Date: Tue, 16 May 2023 05:16:27 -0700 To: Olivier Dion Message-ID: <67447df6-11a8-4315-8357-d1127c80798f@paulmck-laptop> References: <87v8gzuc3g.fsf@laura> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87v8gzuc3g.fsf@laura> Subject: Re: [lttng-dev] [RFC] Deprecating RCU signal flavor X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Paul E. McKenney via lttng-dev" Reply-To: paulmck@kernel.org Cc: lttng-dev Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" On Wed, May 10, 2023 at 05:10:27PM -0400, Olivier Dion wrote: > Hi all, > > We have the intention of deprecating the urcu-signal flavor in the > future. We are asking users of URCU for _feedback_ on this before > going any further. > > Part of this decision is that we are adding support for TSAN in URCU and > the signal flavor deadlocks with TSAN. It is also my understanding that > the urcu-signal flavor was historically made as a fallback for system > lacking the membarrier(2) system call. Nowadays, most systems have > support for that system call, making the urcu-signal an artifact of the > past. No objections here. I will need to do a little rework of my book, but I can do that. ;-) > The following is a proposed timeline of events: > > 1. Asking for feedback from users of URCU (this message) > 2. Disabling the signal flavor by default and adding --enable-flavor-signal > 3. Removing the signal flavor Makes sense to me! Thanx, Paul _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev