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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92383C3279B for ; Mon, 2 Jul 2018 18:05:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4B9602502D for ; Mon, 2 Jul 2018 18:05:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4B9602502D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753183AbeGBSFf (ORCPT ); Mon, 2 Jul 2018 14:05:35 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:33780 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753068AbeGBSFe (ORCPT ); Mon, 2 Jul 2018 14:05:34 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 544DF401EF0D; Mon, 2 Jul 2018 18:05:33 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.34.27.30]) by smtp.corp.redhat.com (Postfix) with SMTP id 5AC762166B5D; Mon, 2 Jul 2018 18:05:30 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Mon, 2 Jul 2018 20:05:33 +0200 (CEST) Date: Mon, 2 Jul 2018 20:05:29 +0200 From: Oleg Nesterov To: Srikar Dronamraju Cc: Ravi Bangoria , rostedt@goodmis.org, mhiramat@kernel.org, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, linux-kernel@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org, ananth@linux.vnet.ibm.com, alexis.berlemont@gmail.com, naveen.n.rao@linux.vnet.ibm.com, linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org, linux@armlinux.org.uk, ralf@linux-mips.org, paul.burton@mips.com Subject: Re: [PATCH v5 06/10] Uprobes: Support SDT markers having reference count (semaphore) Message-ID: <20180702180529.GB31400@redhat.com> References: <20180628052209.13056-1-ravi.bangoria@linux.ibm.com> <20180628052209.13056-7-ravi.bangoria@linux.ibm.com> <20180702160158.GD65296@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180702160158.GD65296@linux.vnet.ibm.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 02 Jul 2018 18:05:33 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 02 Jul 2018 18:05:33 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'oleg@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/02, Srikar Dronamraju wrote: > > > Implement the reference counter logic in core uprobe. User will be > > able to use it from trace_uprobe as well as from kernel module. New > > trace_uprobe definition with reference counter will now be: > > > > :[(ref_ctr_offset)] > > > > where ref_ctr_offset is an optional field. For kernel module, new > > variant of uprobe_register() has been introduced: > > > > uprobe_register_refctr(inode, offset, ref_ctr_offset, consumer) > > > > Sorry for bringing this again, but I would actually think the ref_ctr is > a consumer property. i.e the ref_ctr_offset should be part of > uprobe_consumer. Damn yes ;) I was thinking about this too but decided to discuss this later. But this probably means more complications, I am not sure about the actual implementation. Oleg. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 3D05B7D043 for ; Mon, 2 Jul 2018 18:05:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753100AbeGBSFe (ORCPT ); Mon, 2 Jul 2018 14:05:34 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:33780 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753068AbeGBSFe (ORCPT ); Mon, 2 Jul 2018 14:05:34 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 544DF401EF0D; Mon, 2 Jul 2018 18:05:33 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.34.27.30]) by smtp.corp.redhat.com (Postfix) with SMTP id 5AC762166B5D; Mon, 2 Jul 2018 18:05:30 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Mon, 2 Jul 2018 20:05:33 +0200 (CEST) Date: Mon, 2 Jul 2018 20:05:29 +0200 From: Oleg Nesterov To: Srikar Dronamraju Cc: Ravi Bangoria , rostedt@goodmis.org, mhiramat@kernel.org, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, linux-kernel@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org, ananth@linux.vnet.ibm.com, alexis.berlemont@gmail.com, naveen.n.rao@linux.vnet.ibm.com, linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org, linux@armlinux.org.uk, ralf@linux-mips.org, paul.burton@mips.com Subject: Re: [PATCH v5 06/10] Uprobes: Support SDT markers having reference count (semaphore) Message-ID: <20180702180529.GB31400@redhat.com> References: <20180628052209.13056-1-ravi.bangoria@linux.ibm.com> <20180628052209.13056-7-ravi.bangoria@linux.ibm.com> <20180702160158.GD65296@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180702160158.GD65296@linux.vnet.ibm.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 02 Jul 2018 18:05:33 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 02 Jul 2018 18:05:33 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'oleg@redhat.com' RCPT:'' Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 07/02, Srikar Dronamraju wrote: > > > Implement the reference counter logic in core uprobe. User will be > > able to use it from trace_uprobe as well as from kernel module. New > > trace_uprobe definition with reference counter will now be: > > > > :[(ref_ctr_offset)] > > > > where ref_ctr_offset is an optional field. For kernel module, new > > variant of uprobe_register() has been introduced: > > > > uprobe_register_refctr(inode, offset, ref_ctr_offset, consumer) > > > > Sorry for bringing this again, but I would actually think the ref_ctr is > a consumer property. i.e the ref_ctr_offset should be part of > uprobe_consumer. Damn yes ;) I was thinking about this too but decided to discuss this later. But this probably means more complications, I am not sure about the actual implementation. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: oleg@redhat.com (Oleg Nesterov) Date: Mon, 2 Jul 2018 20:05:29 +0200 Subject: [PATCH v5 06/10] Uprobes: Support SDT markers having reference count (semaphore) In-Reply-To: <20180702160158.GD65296@linux.vnet.ibm.com> References: <20180628052209.13056-1-ravi.bangoria@linux.ibm.com> <20180628052209.13056-7-ravi.bangoria@linux.ibm.com> <20180702160158.GD65296@linux.vnet.ibm.com> Message-ID: <20180702180529.GB31400@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 07/02, Srikar Dronamraju wrote: > > > Implement the reference counter logic in core uprobe. User will be > > able to use it from trace_uprobe as well as from kernel module. New > > trace_uprobe definition with reference counter will now be: > > > > :[(ref_ctr_offset)] > > > > where ref_ctr_offset is an optional field. For kernel module, new > > variant of uprobe_register() has been introduced: > > > > uprobe_register_refctr(inode, offset, ref_ctr_offset, consumer) > > > > Sorry for bringing this again, but I would actually think the ref_ctr is > a consumer property. i.e the ref_ctr_offset should be part of > uprobe_consumer. Damn yes ;) I was thinking about this too but decided to discuss this later. But this probably means more complications, I am not sure about the actual implementation. Oleg.