Received: by 10.223.185.116 with SMTP id b49csp6101291wrg; Wed, 28 Feb 2018 04:07:22 -0800 (PST) X-Google-Smtp-Source: AH8x224xJYAsgg9chWdjwB7j4RsbF7bP3SUFRN7Y7VpG95lVZaaLfxe9VCFzH/iLhchjSQETQZpV X-Received: by 2002:a17:902:8c97:: with SMTP id t23-v6mr17840559plo.372.1519819642360; Wed, 28 Feb 2018 04:07:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519819642; cv=none; d=google.com; s=arc-20160816; b=YTXtKVdis/WUkvS15EKntGIvJBTtggZJvoWdIoB1nafKTj9LsZFPhI+hrQL8dyMit+ Lcrd1AInL1aQdZP782glUKGSVCQef5VfkW2Gp8zWqPQuIsw2RmZ/dfqYbIdB2RmuoPBA +ac6xxKY1ANv8IYxEI0y562Jkndp9jDmxzMumsj01CmVzadIWuA3ndao2eoGXoWa9D9f oybGk3k3AFhBk2yfgaE2s2Zf7CFx28DmLRfuJ9EoGoX3VZm/A3aSK8q+2CgujOlD88Jl QGPl2KqXoOsnA/Z4WEuo2LGn81WrorJFV9Na2ZD1tyKB7EKVcWuxe5saGJNnl8y5oDIK 1dHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:subject:cc:to :from:date:arc-authentication-results; bh=gGaLFSLIgHcuPSHxEdtbxxaN59bAqR4UcqKbCRM5PCI=; b=gUAyJpiA1UsG7P1/YATaW5zxiRmp+5KFL35s4oDIGl4HAcAMeEbHQzKm8zLcNKm8uN ubytaGtI2LiL9S70W38vD2vxZTZxe19qZ/LLXLachI/98tTnGrIRcl8wsodOjWlYY6WZ ajmn5V4ou2jq5UqO+MuKOH7YXB44HeUK63ATcyPXon7p5xJ+dk4nD03EWwQbJoYAp/bf fdqaiwwsuf3izQXaFpzDDlR67y4Jzu0uzqv8RWvvY5SU9FNqwq6xGNbLaUh2p9acEbps pirkNfpPlexQp8GPlnm03BCjWjtDl76IWQ6sGSG6M8pwzMmNCPDq4IVlQaAQeP+P/1wF /jfQ== 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 p8-v6si1180646plk.192.2018.02.28.04.07.05; Wed, 28 Feb 2018 04:07:22 -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 S1752279AbeB1MGY (ORCPT + 99 others); Wed, 28 Feb 2018 07:06:24 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:52158 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752192AbeB1MGW (ORCPT ); Wed, 28 Feb 2018 07:06:22 -0500 Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w1SBxJAW105675 for ; Wed, 28 Feb 2018 07:06:22 -0500 Received: from e06smtp12.uk.ibm.com (e06smtp12.uk.ibm.com [195.75.94.108]) by mx0b-001b2d01.pphosted.com with ESMTP id 2gdtvekc4u-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Wed, 28 Feb 2018 07:06:20 -0500 Received: from localhost by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 28 Feb 2018 12:06:18 -0000 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp12.uk.ibm.com (192.168.101.142) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 28 Feb 2018 12:06:15 -0000 Received: from d06av26.portsmouth.uk.ibm.com (d06av26.portsmouth.uk.ibm.com [9.149.105.62]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w1SC6EfT57278498; Wed, 28 Feb 2018 12:06:14 GMT Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AB31BAE05A; Wed, 28 Feb 2018 11:56:59 +0000 (GMT) Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A6109AE05D; Wed, 28 Feb 2018 11:56:57 +0000 (GMT) Received: from linux.vnet.ibm.com (unknown [9.40.192.68]) by d06av26.portsmouth.uk.ibm.com (Postfix) with SMTP; Wed, 28 Feb 2018 11:56:57 +0000 (GMT) Date: Wed, 28 Feb 2018 04:06:17 -0800 From: Srikar Dronamraju To: Ravi Bangoria 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 Subject: Re: [RFC 0/4] trace_uprobe: Support SDT markers having semaphore Reply-To: Srikar Dronamraju References: <20180228075345.674-1-ravi.bangoria@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20180228075345.674-1-ravi.bangoria@linux.vnet.ibm.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-TM-AS-GCONF: 00 x-cbid: 18022812-0008-0000-0000-000004D57706 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18022812-0009-0000-0000-00001E689B4E Message-Id: <20180228120617.GA63063@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-02-28_07:,, 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=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1802280145 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * 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?