Received: by 10.223.185.116 with SMTP id b49csp7018206wrg; Wed, 28 Feb 2018 21:09:35 -0800 (PST) X-Google-Smtp-Source: AG47ELtjN6IPTL7QinoXlPkM/rAA4kaXpiHdq0OiEy+HMLOCBbzzc0u9tC3tL4MfayXliyHR/x+0 X-Received: by 2002:a17:902:63:: with SMTP id 90-v6mr683541pla.125.1519880975822; Wed, 28 Feb 2018 21:09:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519880975; cv=none; d=google.com; s=arc-20160816; b=OVWcLJeKxMBtF6oZ5BUvDfu1ZUxRp13NK/eSmiU20YtQs+hgXxdgWp3tcjjg/avDOd YGSJpt1+CF0V42RQV6HP8crhIdmsPtKQn726YErAq9dpGnqEjo/YCKvbw4gHjWT8X3+U ZQMruQmdLllGJpwvT6TbP/Q2c4DCpEJtGiUc3/fqDFoekyCMSsErHye8Mo6fjA+1+GvD 3lkwP+fvLJ38quPW8HQ56DZjg4MT0ts+l8aGRNVpXJwyYsEsHXmy0FaJOz7Ir+wZCcN9 QFqmQhwWP/YQWXgXOsx5wUeuR6YAXf8EYkorHZPaN5PIcplau7qX0sTOiwjkIqSsq760 oATw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :references:cc:to:subject:from:arc-authentication-results; bh=TpCEJtlkKppcOcB/cQTLyNNnFrpMTZ9+3atSrVZm/Yw=; b=inRsJfoi6OYBpO1vQni74GgOb3ZR+/AKBxL7VQM6N9QTo0fctVHg8Ab6uPV/Coh5jx J9MfKsXauy9Ug/dUc1CKGSduDXsUQdtdQgadBo6ywTuwyfFAyx0ZgpCy4Ex4+fDuSkxN rP65SQbm7hOiTsRNGI7J0ZsD+i1WRmpJS6ZTsz1PMus/ZY3Bd4/JEz+Kdpn2Ji5Y/Gbl AgUfAE8zFHKMHAVnVjDSneuSXEkt0BjDJWsuP1GClownj7UMREIioFZaTrCm/acjUqhr PEpn8khOO4v1SgHzMtDE/x1FCD8NQF/wc/1sVTalooJChDpMkKyl7xilbCZpZU54toOS rNtQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d62si145089pga.631.2018.02.28.21.09.21; Wed, 28 Feb 2018 21:09:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965979AbeCAFIn (ORCPT + 99 others); Thu, 1 Mar 2018 00:08:43 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:40744 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932086AbeCAFIl (ORCPT ); Thu, 1 Mar 2018 00:08:41 -0500 Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2154WpA100134 for ; Thu, 1 Mar 2018 00:08:41 -0500 Received: from e06smtp14.uk.ibm.com (e06smtp14.uk.ibm.com [195.75.94.110]) by mx0a-001b2d01.pphosted.com with ESMTP id 2ge97ckkbp-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Thu, 01 Mar 2018 00:08:41 -0500 Received: from localhost by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 1 Mar 2018 05:08:38 -0000 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp14.uk.ibm.com (192.168.101.144) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 1 Mar 2018 05:08:34 -0000 Received: from d06av22.portsmouth.uk.ibm.com (d06av22.portsmouth.uk.ibm.com [9.149.105.58]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w2158YX264225512; Thu, 1 Mar 2018 05:08:34 GMT Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9CBE74C052; Thu, 1 Mar 2018 05:02:02 +0000 (GMT) Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5646E4C046; Thu, 1 Mar 2018 05:02:00 +0000 (GMT) Received: from [9.124.31.169] (unknown [9.124.31.169]) by d06av22.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 1 Mar 2018 05:02:00 +0000 (GMT) From: Ravi Bangoria Subject: Re: [RFC 0/4] trace_uprobe: Support SDT markers having semaphore To: Srikar Dronamraju Cc: 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, rostedt@goodmis.org, mhiramat@kernel.org, ananth@linux.vnet.ibm.com, naveen.n.rao@linux.vnet.ibm.com, oleg@redhat.com, Ravi Bangoria References: <20180228075345.674-1-ravi.bangoria@linux.vnet.ibm.com> <20180228120617.GA63063@linux.vnet.ibm.com> Date: Thu, 1 Mar 2018 10:40:43 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180228120617.GA63063@linux.vnet.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 18030105-0016-0000-0000-0000052B4502 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18030105-0017-0000-0000-000028684789 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-01_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1803010064 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/28/2018 05:36 PM, Srikar Dronamraju wrote: > * Ravi Bangoria [2018-02-28 13:23:41]: > >> # readelf -n ./tick >> Provider: tick >> Name: loop2 >> ... Semaphore: 0x0000000010020036 >> >> # readelf -SW ./tick | grep probes >> [25] .probes PROGBITS 0000000010020034 010034 >> >> >> Semaphore offset is 0x10036. I don't have educated 'perf probe' >> about semaphore. So instead of using 'perf probe' command, I'm >> manually adding entry in the /uprobe_events file. >> Special char * denotes semaphore offset. >> >> >> # echo "p:sdt_tick/loop2 /tmp/tick:0x6e4 *0x10036" > uprobe_events >> >> # perf stat -e sdt_tick:loop2 -- /tmp/tick >> hi: 0 >> hi: 1 >> hi: 2 >> hi: 3 >> ^C >> Performance counter stats for '/tmp/tick': >> 4 sdt_tick:loop2 >> 3.359047827 seconds time elapsed >> >> >> Feedback? >> >> TODO: >> - Educate perf tool about semaphore. >> > Is it possible to extend perf buildcache with a new option to work with > semaphore? Yes, that should be fairly easy to do. Will add a patch for that. Thanks for the review, Ravi