Received: by 10.223.185.116 with SMTP id b49csp2604388wrg; Mon, 5 Mar 2018 05:55:09 -0800 (PST) X-Google-Smtp-Source: AG47ELtugbD7MDzzsML4PsyXiy7pxX/YIo/IZo+hyVAY7sy7bGHbunrAawTvuXryQmCicrB93wOU X-Received: by 10.101.82.195 with SMTP id z3mr12471399pgp.308.1520258109504; Mon, 05 Mar 2018 05:55:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520258109; cv=none; d=google.com; s=arc-20160816; b=igz+HJmWNhG5Lat+Nm6dXk7UbkrUtjZauAtDOQXePv+LECe3ZOOB+VeHt8Wux6w5Um xsOj6KsvyH6kii4pK+UQYnNy4RWU0gkz/cnFF5eboszEZ9MRgfvFvWQ+QduIkplFgWXS 98G86EgbQIMHED7zo9wcavoW15Qloub4g5cxUP/Ax7dhESeZf1N9H5gqmgmgC0m97pOa 9RraZnfv0CTDctZwWKhsoTRVYehbAFpzUcDzjCuZXJ+etLw1kop1Ezq0Qz+7f99uAa1j ch9yYl82nM8RewvRGPIl8SFZZ5D8y3piBJSZGXD6Pyv0WC94aejWvJfL7JLf2jCDH4BK W6rg== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:arc-authentication-results; bh=PPOfI+F9UlThPs8e65tPir2bv64Puwb8KUeDLndIRgs=; b=cgyVByRXuzk8BrXh36nkN9agOqOK2tAsL1MzqrmCa+F4IV5PKClupnvymOmawZ0JCA +4YyEgm4MyaVSaBtNazQyukfFMnHtZirrBvQzd7weFX/H136C6qMr6t+FmOMRgccU9Uh dxxYyAVyEti6dOoC3xt7b+WIp70dBfwXbkG93w6mY+VLQZ2odLx3yjRUXCBP1eOjHBhF RIFokvwGloYYwdPk7xo0fZkN+VCOe/oOTyEtPFxV5k6acWmDQxeG7Tczc3haDni09CwH o5gr5sFxk2nXYqqtvzo2lh27KHFnDvWmtLjxtF+08ztGOtfHnwA05OG39ont5zseBPL8 BDhQ== 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 v4-v6si9309119plo.55.2018.03.05.05.54.55; Mon, 05 Mar 2018 05:55:09 -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 S934161AbeCELYq (ORCPT + 99 others); Mon, 5 Mar 2018 06:24:46 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:40289 "EHLO huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S933983AbeCELYp (ORCPT ); Mon, 5 Mar 2018 06:24:45 -0500 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 9592E8298807D; Mon, 5 Mar 2018 19:24:29 +0800 (CST) Received: from [127.0.0.1] (10.202.227.238) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.361.1; Mon, 5 Mar 2018 19:24:21 +0800 Subject: Re: [PATCH v2 00/11] perf events patches for improved ARM64 support To: William Cohen , Ganapatrao Kulkarni , Jiri Olsa References: <1519401932-205051-1-git-send-email-john.garry@huawei.com> <20180227095028.GG21033@krava> <6250a69e-71ab-5119-cc3f-7e2661aa8c0b@huawei.com> <8f72afe5-8620-bdd3-3a54-87a22f77c3d4@redhat.com> CC: Ganapatrao Kulkarni , , Peter Zijlstra , Will Deacon , Linuxarm , "Arnaldo Carvalho de Melo" , , Zhangshaokun , Alexander Shishkin , Ingo Molnar , , , From: John Garry Message-ID: <599637d9-0b78-9edb-d459-515f76aca9fe@huawei.com> Date: Mon, 5 Mar 2018 11:24:13 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <8f72afe5-8620-bdd3-3a54-87a22f77c3d4@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.238] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> I am seeing issue(log below) with this patchset on our platfrom. >> i have tried using your v2 branch [1] >> >> root@borg-1>perf_acme>> ./perf --version >> perf version 4.16.rc1.g087f7ca >> root@borg-1>perf_acme>> ./perf stat -e bus_access_rd sleep 1 >> >> Performance counter stats for 'sleep 1': >> >> 23,099 bus_access_rd >> >> 1.000708516 seconds time elapsed >> >> root@borg-1>perf_acme>> cd - >> /ganapat/perf/linux-hisi/tools/perf >> root@borg-1>perf>> ./perf --version >> perf version 4.16.rc1.gcb5a74 >> root@borg-1>perf>> ./perf stat -e bus_access_rd sleep 1 >> >> Performance counter stats for 'sleep 1': >> >> 0 bus_access_rd >> >> 1.000709162 seconds time elapsed >> >> root@borg-1>perf>> >> >> >> [1] https://github.com/hisilicon/linux-hisi.git >> > Hi, Hi Will Cohen, Ganapatrao, > > I took a slightly different tack and compared the output of "perf list --details" to see if the event numbers numbers were the same. For the common events borrowed from the armv8-recommended.json all the events are 0 for the cortex a53. That would explain why the bus_access_rd above were counts were different if it was counting the SW_INCR event instead of bus_access_rd. > Thanks for this. I see the problem. At the end I missed bringing across something from v1. Easily fixed. > Why not key the matching of common events off the "EventName" rather than "EventCode"? The EventName would be more descriptive. Then the json files could eliminate the "BriefDescription" and just have the EventName with nothing else for each event. This would further reduce the amount of redundant fields between the specific implementations and the common set. > I did consider it and it could work. But it all depends on whether the "EventName" only is always readable/descriptive enough in the JSON, without requiring the "BriefDescription". The "EventName" can be rather succinct for any arch. And we need to guarantee that the "EventName" is unique. Here's a sample: [ { "ArchStdEvent": "L1D_CACHE_RD", }, { "ArchStdEvent": "L1D_CACHE_WR", }, vs. [ { "ArchStdEvent": "0x40", "BriefDescription": "L1D cache access, read" }, { "ArchStdEvent": "0x41", "BriefDescription": "L1D cache access, write" }, Opinion? John > -Will > > . > thanks, John