Received: by 10.223.164.202 with SMTP id h10csp1198704wrb; Tue, 7 Nov 2017 23:58:33 -0800 (PST) X-Google-Smtp-Source: ABhQp+TNEkx5vDP6iHQUUVLu5JYTYyFRiifHqw83nwdL0xwVyBvJgOR7ZCvQp032bNOIPpT+kSAm X-Received: by 10.101.77.75 with SMTP id j11mr1191944pgt.141.1510127913208; Tue, 07 Nov 2017 23:58:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510127913; cv=none; d=google.com; s=arc-20160816; b=dpH+WVjlrO+FdDZo0MPkt7G2jNq5atOYheatiHofNSGbni6U/XlcNnMtfjwkkQ/FQa QtHfpNqA9eIVva57Aoh+eXq0HsOcuWgKOI/woF3nKJozk7YMm/U0IZoijl70CzCH1T7U qeJCXupr8iUfw0i42UyWZ20ADJp5+5NztYSuPdduId63pkMZWFtq3f8RZv3Y96mdse1F 6wg62iateYUkfCdTbBouXxQF8aOf4yLkVKMnVKdej4k4u+WGQqK5Hj0+5i5LQsi8Od20 kPkGYIGb1UTqQmih3GtlKQZBqxdnsGQIJkXUle2VvejIrSnDElJQBS4YSa9CVsenkDeO KFhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=0tpytwvd1UouGzkM7iGMfsCNsOIpxbHzVfyvmhfCX8Q=; b=FEmaFRzGaQKw43nf5hofhbtp1j0ob/kf26KJN62uxNBXoc8nhymlvm7tRN0YkkF45y b2xSv1HIcdPtNczxS4Y+LkO6RjameHgV7MzZCNRcqiFzbw8WYsT0uDG1wDEpD/lh9Uzy ZU4CRf8xqJMaU6gFQEu7SVdzHOMqSGlJEd+GS57FaBxiTkqbtfXaBxprbcFH21pihudI HHxK5KZ9fvwYazt/+BA+Di4EfRR+yqP+nmGV0EWQ866AjoKfuVbw50eZSqR7XHMlnzur emv42exNCygsj0TYbXn0+/U/7UnSsj/5dmetm2q5qAPHH+1KdNFo84MqlnoIBRh2hQsN E1Lg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=ui7bUOoh; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p13si3137315pgn.796.2017.11.07.23.58.20; Tue, 07 Nov 2017 23:58:33 -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; dkim=pass header.i=@google.com header.s=20161025 header.b=ui7bUOoh; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751377AbdKHH50 (ORCPT + 89 others); Wed, 8 Nov 2017 02:57:26 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:52816 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751143AbdKHH4w (ORCPT ); Wed, 8 Nov 2017 02:56:52 -0500 Received: by mail-pg0-f68.google.com with SMTP id a192so1261136pge.9 for ; Tue, 07 Nov 2017 23:56:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=0tpytwvd1UouGzkM7iGMfsCNsOIpxbHzVfyvmhfCX8Q=; b=ui7bUOohk/WH+yxyKQJbNBE4wlDLF8B+SrnJsfKdINTX4J0XQ8j7WN/xk8E2eZZzCp D6rJYbkKXoZaQ9FJ/d7cx0cCIsilW/rlWx/nMGQezHmhBrQuDoyiwRowFazFKrOV5YAE OisG3ULVsUDtttIp4JTIwmWTi5XsY9KVfzlNmwHjlbw32esbW+/UNpdoI6ssD1I96GHA 7YolmcV7vMTReURXCO3JH5LB7k72GLqY3a/1ySIflSdSnpo0B3QkeMDSdf81/qNj7gBH HFYIrX/Hg4XjRL6m5MtD7vG50jYJB2kOfM3dBjPBS18AlfbWpu8Ac0ccXx3EC1qOcX1s 99xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=0tpytwvd1UouGzkM7iGMfsCNsOIpxbHzVfyvmhfCX8Q=; b=DB7ujJAVZwetl6zEQiiUpYacsZwM1+Mqy4XCgVjMGJsqfpiUBX2qrPVwofWXb/MTwk x+EFkoGqWjPero2rXWbkfQPzUUj/HbD73wg7mws/jRdeY/xlUTYPG8sgP9mMSGpEQIA4 ibmk/J/w1yqLb/9ydUUJlLZ4Jp/X71D+wvNjP0cckfJOgBkwMv8tX+Fw9XNROKsaaMfJ NITRCRFSl9ENUUbAC7vnccmG56HdBACYLI+H6UPlZRqDTRJTZFNphoQg2/h56FQFsRHy SYJlNiFOa9gTT0ZN5m24nlzoGnW2uu6oiIaTEuUpMOE5twQm+GU7yL+c8CnK1CmQ+9An wAbg== X-Gm-Message-State: AJaThX7QMcmjKFvOb177Ly5pc5i8/CG6gUlu4R+Wbm5WWiEO33zSFX9B qw6Kh9egxTG9V4OsYMQTl2jHJjiqoJk= X-Received: by 10.98.214.143 with SMTP id a15mr1615885pfl.154.1510127811261; Tue, 07 Nov 2017 23:56:51 -0800 (PST) Received: from localhost (c-67-169-55-77.hsd1.ca.comcast.net. [67.169.55.77]) by smtp.gmail.com with ESMTPSA id d23sm2205982pfk.106.2017.11.07.23.56.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 23:56:50 -0800 (PST) From: Stephane Eranian To: linux-kernel@vger.kernel.org Cc: acme@redhat.com, peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com, kan.liang@intel.com, jolsa@redhat.com Subject: [PATCH v3 4/5] perf/record: add documentation for sampling skid ip Date: Tue, 7 Nov 2017 23:56:36 -0800 Message-Id: <1510127797-22483-5-git-send-email-eranian@google.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1510127797-22483-1-git-send-email-eranian@google.com> References: <1510127797-22483-1-git-send-email-eranian@google.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch adds documentation to describe how to use the skid ip support with perf record. The sample type can be provided per event as follows: pmu_instance/...,skid-ip=1/ For instance on Intel X86: $ perf record -e cpu/event=0xc5,skid-ip=1/pp does record the precise address of retired branches and their target. Signed-off-by: Stephane Eranian --- tools/perf/Documentation/perf-record.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt index 5a626ef666c2..3b156fa03c99 100644 --- a/tools/perf/Documentation/perf-record.txt +++ b/tools/perf/Documentation/perf-record.txt @@ -57,6 +57,14 @@ OPTIONS FP mode, "dwarf" for DWARF mode, "lbr" for LBR mode and "no" for disable callgraph. - 'stack-size': user stack size for dwarf mode + - 'skid_ip' : boolean, captures the unmodified interrupt instruction pointer + (IP) in each sample. Usually with event-based sampling, the IP + has skid and rarely point to the instruction which caused the + event to overflow. On some architectures, the hardware can eliminate + the skid and perf_events returns it as the IP with precise sampling is + enabled. But for certain measurements, it may be useful to have both + the correct and skid ip. This option enable capturing the skid ip in + additional to the corrected ip. Default is: false See the linkperf:perf-list[1] man page for more parameters. -- 2.7.4 From 1583388206842246506@xxx Tue Nov 07 06:37:45 +0000 2017 X-GM-THRID: 1583372847586539879 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread