Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3888503ybl; Mon, 13 Jan 2020 04:28:46 -0800 (PST) X-Google-Smtp-Source: APXvYqyVLgkC1u2lFqLLIBsATkQYKBg++qEsgaTnek5asQRa1zOb+nbRy3BvgEGVTyV5GWUKuQf5 X-Received: by 2002:a9d:6a41:: with SMTP id h1mr12158322otn.279.1578918526836; Mon, 13 Jan 2020 04:28:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578918526; cv=none; d=google.com; s=arc-20160816; b=jYitRflKv5Z7YAD/MZ2L1/nfTI7YTm5Hbjp7n9mZ5d7JkFioQxctVa2ivvuN4YV5wC /yYOkgNCIHVqx7kaeT2m1fBnwA3fdpd4392JrcPFO2VULpQoiPRCm2muQKKs7Ea7XO+P gPM0+B7nTYdJofzwflVwzl68SrwMzRcU2AWDn5sNe8c9ciB9UreJp2UScdMway/f9SDj vug8ZOHxjiceotCf+mUXb/FZXAM2ejBAQC865hDo71O/+2FunLdOokIsDRaVeO/eZGiK 0vZIuGvrkDU8zFBNNsoawuEpoPdgQph7fD8xZsiXYLk0yQbyiMyPDsMDL6H25Ok3OLrL tKGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=apN0l5o565qM6eNfwXsiqaiE9yYLcgAk540nAx9G7zI=; b=ItGYpHJipcfstWaXg+5f+AV9YVYJXPkTzgoi/vI1+EsLVtKqAp8+a3LzViKrc7wjdK YpEaAa96njl7uaMkHQtaz/zxPbCnh8XxH/vaexqh0mLTf/A02kfYd0UyYD2tOTWPWR4V UxDPlgXpBqPac8JdkY/mk10oWA8iCU2SaIOF+ycOzpzPpMZX83wluJJ068THy9G7MNTv hCsD0N8Bqjfl0pvkwaW16IFUTE8Ppd4VjJK5NqyP86oNgRlS0qDQ1IqFijbrzZCOT+Sf wfZDAV8Dzg8WXacF70RpqmPRO6OhMrHM6N8XUdFAL7vnHegtFrpl1dDb2PUKVgI3Zy0A 9X7w== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b11si5997207oie.152.2020.01.13.04.28.35; Mon, 13 Jan 2020 04:28:46 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728512AbgAMM1m (ORCPT + 99 others); Mon, 13 Jan 2020 07:27:42 -0500 Received: from foss.arm.com ([217.140.110.172]:38796 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726399AbgAMM1m (ORCPT ); Mon, 13 Jan 2020 07:27:42 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5595913D5; Mon, 13 Jan 2020 04:27:41 -0800 (PST) Received: from [10.1.197.1] (ewhatever.cambridge.arm.com [10.1.197.1]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 92EBD3F68E; Mon, 13 Jan 2020 04:27:39 -0800 (PST) Subject: Re: [PATCH] perf tools: Fix bug when recording SPE and non SPE events To: Leo Yan , James Clark Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, nd@arm.com, Mathieu Poirier , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Igor Lubashev References: <20191220110525.30131-1-james.clark@arm.com> <20191223034852.GB3981@leoy-ThinkPad-X240s> From: Suzuki Kuruppassery Poulose Message-ID: Date: Mon, 13 Jan 2020 12:27:38 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <20191223034852.GB3981@leoy-ThinkPad-X240s> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Leo, On 23/12/2019 03:48, Leo Yan wrote: > Hi James, > > On Fri, Dec 20, 2019 at 11:05:25AM +0000, James Clark wrote: >> This patch fixes an issue when non Arm SPE events are specified after an >> Arm SPE event. In that case, perf will exit with an error code and not >> produce a record file. This is because a loop index is used to store the >> location of the relevant Arm SPE PMU, but if non SPE PMUs follow, that >> index will be overwritten. Fix this issue by saving the PMU into a >> variable instead of using the index, and also add an error message. >> >> Before the fix: >> ./perf record -e arm_spe/ts_enable=1/ -e branch-misses ls; echo $? >> 237 >> >> After the fix: >> ./perf record -e arm_spe/ts_enable=1/ -e branch-misses ls; echo $? >> ... >> 0 > > Just bring up a question related with PMU event registration. Let's > see the DT binding in arch/arm64/boot/dts/arm/fvp-base-revc.dts: > > spe-pmu { > compatible = "arm,statistical-profiling-extension-v1"; > interrupts = ; > }; > > > Now SPE registers PMU event for every CPU; seem to me, though SPE is an Do you mean "SPE PMU" here ? SPE is different from ETM, where the trace data is micro-architecture dependent. And thus you cannot mix the trace on different CPUs with different micro-archs. As such I don't see any issue with this patch. Suzuki