From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A1B96C433FE for ; Tue, 22 Mar 2022 12:59:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235077AbiCVNAx (ORCPT ); Tue, 22 Mar 2022 09:00:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235057AbiCVNAu (ORCPT ); Tue, 22 Mar 2022 09:00:50 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ADDE05EBC7; Tue, 22 Mar 2022 05:59:21 -0700 (PDT) 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 ams.source.kernel.org (Postfix) with ESMTPS id B4898B81CE8; Tue, 22 Mar 2022 12:59:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C2637C340EE; Tue, 22 Mar 2022 12:59:16 +0000 (UTC) Date: Tue, 22 Mar 2022 08:59:15 -0400 From: Steven Rostedt To: Namhyung Kim Cc: Peter Zijlstra , Boqun Feng , Ingo Molnar , Will Deacon , Waiman Long , LKML , Thomas Gleixner , Byungchul Park , "Paul E. McKenney" , Mathieu Desnoyers , Arnd Bergmann , Radoslaw Burny , linux-arch , bpf Subject: Re: [PATCH 2/2] locking: Apply contention tracepoints in the slow path Message-ID: <20220322085915.6c2e7ff9@gandalf.local.home> In-Reply-To: References: <20220316224548.500123-1-namhyung@kernel.org> <20220316224548.500123-3-namhyung@kernel.org> <20220318180750.744f08d4@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Mon, 21 Mar 2022 22:31:30 -0700 Namhyung Kim wrote: > > Thanks for the info. But it's unclear to me if it provides the custom > > event with the same or different name. Can I use both of the original > > and the custom events at the same time? Sorry, missed your previous question. > > I've read the code and understood that it's a separate event that can > be used together. Then I think we can leave the tracepoint with the > return value and let users customize it for their needs later. Right, thanks for looking deeper at it. -- Steve