From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 52F50C4332F for ; Mon, 11 Dec 2023 21:11:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344835AbjLKVLE (ORCPT ); Mon, 11 Dec 2023 16:11:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345062AbjLKVK4 (ORCPT ); Mon, 11 Dec 2023 16:10:56 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 580EABE for ; Mon, 11 Dec 2023 13:11:01 -0800 (PST) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CA9D7C433C8; Mon, 11 Dec 2023 21:11:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1702329061; bh=a+qGimpcS1XQx24G9vOBh4tKYNM6jWiH7OMmuzR5zQQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dP5/9UhPVl6nKQWLoP7qog/NjAcRskX8/RsAWw+CIwmIyJMZ9tJCr9RdFNtnDQLOY Y7YOYzsnlVI0dHl2jUPUrndGfTEQn+hDZ04rGdPtp25pZcI7fVrbaH8iOjm1NE8WFn 3RLq+qVENCKsKrekGqlO0FXZDmd5qnbQNWdePP0ZifyiS01IXcwjTB2v4UVhqHSnFJ Hbrti4gmZrzDAwR9zPkGGLBwidIYlymY/85Q9I93F1Kknz8x18jt/bjitdEQxZhnAh HsjVef6IknRW47P8UGWqOVFdxzrSGvC63F93BeX9TJf8o8P8lvjwbPw63+Phign5qv pEj4JUMDSvYgw== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id 4F04B403EF; Mon, 11 Dec 2023 18:10:58 -0300 (-03) Date: Mon, 11 Dec 2023 18:10:58 -0300 From: Arnaldo Carvalho de Melo To: "Liang, Kan" Cc: Ian Rogers , Mark Rutland , Marc Zyngier , Hector Martin , Namhyung Kim , Linux Kernel Mailing List , linux-perf-users@vger.kernel.org Subject: Re: 'perf top' broken on intel hybrid systems Message-ID: References: <3a8c66ec-537d-4e29-bf08-226dd41b08aa@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a8c66ec-537d-4e29-bf08-226dd41b08aa@linux.intel.com> X-Url: http://acmel.wordpress.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Fri, Dec 08, 2023 at 02:39:37PM -0500, Liang, Kan escreveu: > On 2023-12-08 1:57 p.m., Arnaldo Carvalho de Melo wrote: > > So I finally got a recent Intel hybrid system: > > root@fedora:~# grep -m1 "model name" /proc/cpuinfo > > model name : Intel(R) Core(TM) i7-14700K > > root@fedora:~# > > Most things work, but: > > root@fedora:~# perf top > > Error: > > The cycles:P event is not supported. > > root@fedora:~# > > > > root@fedora:~# perf top -e cycles:p > > Error: > > The cycles:p event is not supported. > > root@fedora:~# perf top -e cycles:pp > > Error: > > The cycles:pp event is not supported. > > ^[[Aroot@fedora:~# perf top -e cycles:ppp > > Error: > > The cycles:ppp event is not supported. > > root@fedora:~# > > root@fedora:~# perf top -e cycles > > Error: > > The cycles event is not supported. > > root@fedora:~# > The error is because the perf top always tries to open an event on the > user_requested_cpus, which are all CPUs by default. But what is wrong with that for the default event, CPU cycles? It should work for all CPUs, its the most basic event, right? We should have a rough idea where CPU (no matter which CPUs) cycles are being used. - Arnaldo