Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp611974pxh; Tue, 9 Nov 2021 16:10:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJwpAup9HahXOA+5zcB+i3D1LQWDK04PhG9AL7WXE0RyT4rU6f+qkgHJmQlgk/7cIBs/SC+g X-Received: by 2002:a05:6602:2a42:: with SMTP id k2mr7752064iov.132.1636503021480; Tue, 09 Nov 2021 16:10:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636503021; cv=none; d=google.com; s=arc-20160816; b=wotW2vOdjmaYdDY2T1D/3lj3cMCexvMdJhmdE2ByEDfgTlpcQTjSqYs/2+6HspKBBs jMaX112GCk2OhTmeeePZg9otMfCIG+RrMFFiozZm7EVx/RgdMT+iutq6gwivufIRg6f7 Ug7oD9zFe6hyvkJvNYTtaIWsROsvHlHh7DGcePBbQZqBkPeDtcu7XMunsHhfZG3MLSvQ YiUgCTDG1g2u0ObOYbl/w3iuZyIg8EL/dzOMrsHwgPJvuxBbrimau6IUYW/5c4nJWeoI 2XoMI5lFgPXWRnUuZYXAh058JWUPT/7dxC9EUvLDJkf+iM7+xziPPR9vti4OAYWyHoYc U+cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=LVuoG6jbkqITSG4RUykh69JXmdYdRLsgMW0EYKwWyb0=; b=dOJzizz4Xv1zJd9pYQeWFSC3kRLfRqez73+SrxvMH/1KPZAy7NHVR3O8WQJR0x7lyx yL3H0LWLf8phG8hxDofcEdhSUq2uQMvONAWblNaieKsOG2Ke8Dw/5Q2u270Rlf6UO3qt nETaV7qNGknWrFpmOYCFpebO1dVBWyRmVkduINhRErhapBsR1lJw2WdV2O07Z1OwjBmp bmaycB08gjnlCEXHOyTlpKxHvC/CcjodQNh1L7bc+1s25V2N86Q0TGUPzYTBdjgNPcud 8Xy5KTS9gfvL7tAffluKJpZYSNHG4OAzpq923ZeKJwe/uTrA+E1X/XVxvjMEkqKz98/1 xPww== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s22si45594589jaj.128.2021.11.09.16.10.09; Tue, 09 Nov 2021 16:10:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240901AbhKIRnh (ORCPT + 97 others); Tue, 9 Nov 2021 12:43:37 -0500 Received: from mail.kernel.org ([198.145.29.99]:47526 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236368AbhKIRng (ORCPT ); Tue, 9 Nov 2021 12:43:36 -0500 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8C7BC61208; Tue, 9 Nov 2021 17:40:49 +0000 (UTC) Date: Tue, 9 Nov 2021 12:40:46 -0500 From: Steven Rostedt To: Sai Prakash Ranjan Cc: Will Deacon , Catalin Marinas , , Marc Zyngier , , , , , , , , Subject: Re: [PATCHv3 3/3] dynamic_debug: Add a flag for dynamic event tracing Message-ID: <20211109124046.2a772bcb@gandalf.local.home> In-Reply-To: <264b77dd-5509-60f9-248c-a93135b01aa9@quicinc.com> References: <3706af20bc64a320ff8f3ff8950738b988f4bdf5.1636452784.git.quic_saipraka@quicinc.com> <20211109104941.2d50eafc@gandalf.local.home> <20211109115951.1c2b5228@gandalf.local.home> <264b77dd-5509-60f9-248c-a93135b01aa9@quicinc.com> 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: linux-kernel@vger.kernel.org On Tue, 9 Nov 2021 23:00:11 +0530 Sai Prakash Ranjan wrote: > Ah that's a very good idea, descriptor does contain the module, file name. > We can probably even pass the module name,file name as string from the > descriptor itself to event? > Perhaps we can do that for all trace events and not just this trace > event? Just like the trace event name displayed > with trace events, perhaps have file name,module name displayed when > dynamic debug is enabled? Filtering by > filename is pretty useful since most of these usecases in debugging will > be with respect to some driver or subsystems. If we add this for all events, it would require a lot of changes to all users of tracepoints, as it would require adding a new parameter to the callbacks. We could add a flag in the registering that states that the callback is OK for it, and it passes that data as well. Let me look into this for a bit. I may not have something this week, but we should look into this more before adding little hacks that do this one at a time like this patch. -- Steve