Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp104771ybl; Tue, 10 Dec 2019 18:37:38 -0800 (PST) X-Google-Smtp-Source: APXvYqxdwUyHDYYgoW0A31+l8iYTR/TC4N+fu+jNjgQskFY4i9YIq+tGwsgirKFet7dbIdkvWUC3 X-Received: by 2002:a9d:1e88:: with SMTP id n8mr699112otn.369.1576031858365; Tue, 10 Dec 2019 18:37:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576031858; cv=none; d=google.com; s=arc-20160816; b=Rmx69HnwP++CcL12Kcw7mPze2/erE6YnofG3yOR4SHq6ccSTUmoqWygAeQXdNu+RXq KZR2mmfpFIenQRfyI2FCskNsQR6Zua+tbzzm34MWPDAEcKqxTHHwCYPJgsRR0iDpI7RU bdsC9X9O9OBPEn3iTqYXzbwl+gxi0a0EiuMtanOrROIcYfvMFkg89SpVB7B8y2f8aQYX wI4v4v14BrQiTnBlrSOWCbGW03Jko+1alOca3DExJNSrXM3ZOgtofzGhTxK2E/NplOHC qP37ckSoV297oc9deme16J8qUTW2GoHv86JoZYAWQFMRDn/92iwF03arcizh18i3c0Po WBBw== 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=Pk6sTDNIKQPrIF0WwRXu19LNnHMgcpTGKlK5o/AAM+8=; b=jYIbDc8rqhYnMlkGMESHEzd7YDFlwS1bZcFMFHFmwkvsTxU1M1upZ7u5ZgAXMN50Ik YQ7lBb2sg05rjcT9N2FAYyZEzVk5tkE8c9LsXdnATJc9+hnbB+y6DdNZwNfG118CbqAb dK0Cynmzo3Nx9On1N2Y0avwvne6ZX+0O76R3JutNTAPkLop55jYNt2G4wosXQPlrD99d EU4N79qJxnVfY0AfMy03WDU53mX6X1kjW9c+93XAWyQJUl0jhb65M2oF6hw7em+jYe53 h9ATV9FdO/3JZFT1S4FzgQGibInRL4StYO/LKvp8sNBAJ8aWH6JdwQh1UNpdf6AjW2T+ ERGA== 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 s22si341574oij.35.2019.12.10.18.37.26; Tue, 10 Dec 2019 18:37:38 -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 S1727336AbfLKCgx (ORCPT + 99 others); Tue, 10 Dec 2019 21:36:53 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:39882 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726619AbfLKCgx (ORCPT ); Tue, 10 Dec 2019 21:36:53 -0500 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id C76F92176297C62AADC0; Wed, 11 Dec 2019 10:36:50 +0800 (CST) Received: from [127.0.0.1] (10.173.222.27) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.439.0; Wed, 11 Dec 2019 10:36:41 +0800 Subject: Re: perf top for arm64? To: Jiri Olsa , John Garry CC: , , Linuxarm , Arnaldo Carvalho de Melo , , "linux-perf-users@vger.kernel.org" , , , , , , References: <1573045254-39833-1-git-send-email-john.garry@huawei.com> <20191106140036.GA6259@kernel.org> <418023e7-a50d-cb6f-989f-2e6d114ce5d8@huawei.com> <20191210163655.GG14123@krava> <952dc484-2739-ee65-f41c-f0198850ab10@huawei.com> <20191210170841.GA23357@krava> From: Zenghui Yu Message-ID: <0870e660-2511-ced0-7402-5ff389c4c281@huawei.com> Date: Wed, 11 Dec 2019 10:36:39 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <20191210170841.GA23357@krava> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.173.222.27] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On 2019/12/11 1:08, Jiri Olsa wrote: > On Tue, Dec 10, 2019 at 04:52:52PM +0000, John Garry wrote: >> On 10/12/2019 16:36, Jiri Olsa wrote: >>> On Tue, Dec 10, 2019 at 04:13:49PM +0000, John Garry wrote: >>>> Hi all, >>>> >>>> I find to my surprise that "perf top" does not work for arm64: >>>> >>>> root@ubuntu:/home/john/linux# tools/perf/perf top >>>> Couldn't read the cpuid for this machine: No such file or directory >>> >> >> Hi Jirka, >> >>> there was recent change that check on cpuid and quits: >>> 608127f73779 perf top: Initialize perf_env->cpuid, needed by the per arch annotation init routine >>> >> >> ok, this is new code. I obviously didn't check the git history... >> >> But, apart from this, there are many other places where get_cpuid() is >> called. I wonder what else we're missing out on, and whether we should still >> add it. > > right, I was just wondering how come vendor events are working for you, > but realized we have get_cpuid_str being called in there ;-) > > I think we should add it as you have it prepared already, > could you post it with bigger changelog that would explain > where it's being used for arm? I've also seen the similar problem when I was looking to add support for 'perf kvm stat' on arm64 [1] (which though got stuck due to some other reasons for a very long time :( It would be great if your patch can address this issue! [1] https://lore.kernel.org/patchwork/patch/1087531/ Thanks, Zenghui