Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp964641pxb; Thu, 9 Sep 2021 16:33:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyQQA9PD2SNS3CiTNvdbEVjZ07yMkjDqA7vfai8V8ZN74ll9M7r9oFD/WBJZG0AcsaNS47g X-Received: by 2002:a05:6638:339b:: with SMTP id h27mr2044586jav.118.1631230423784; Thu, 09 Sep 2021 16:33:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631230423; cv=none; d=google.com; s=arc-20160816; b=eqstShJqYYm4HD+nYER3P88yTUuaQjprJF7ozTecLTvLaoOJEqGiZCHda7J0Ghx6zb 3pcoqboGe9AiQbPlnDm0ZVStcsyb2HNb7Oglm/kkh5W+shIXMP9gQbUwM6RpDljqgDmh kWLFxHW9af7KYn2GQnS7HTlNZB7qSFf+npIseih2MYRQ48ZCwJzXjjcoFZCr7B45s56+ qeCpl8xUuWAr6vK3lX48Hdllw4b6PGIkvqXuFwCV28uY+JokEjQ8ITyw1QZtV3d6YDLt MF6HVnuLxzQlwt10viarf0U6NylvlkrEzMzkcl4NXvbsPSxLMcCHrpVwPm1C2x3+Xf9D 1r+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=8daYscED9Gsv0n+jRYejHVuJNyD1YfNF1MKvfmug2n0=; b=jWYibdMuyScGM2GYOZ3sQq/j1TERYeaeXLZtOoEqKfQzbldj82CSIZhisf+9Zc9EYs 07WgoAWdzGFZ6G3CnQVVNBMt5py1xJA3EYbCqTQqfphfLlzFo2GdOZGMw3rJBUX60h3o 6eV6XKh+MmksJKBIy2w3sbb82m8tOn2r0wZ87L3CROIOxEkPcAU4r/xEfxqTrAAObS1V nauFWYd0xkNpModKSQMce0hmk4e43mCBUUuyRFLmoyIvpSsC9yDGxHNQxcLbh2qVuuN4 YY9GwXZBffS9XeCdAb+yX6FMUOMrrJUd8wRASFyUl0FZULQIKS7HKpF33iKuI2ZdRGo5 at1Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c32si3345999jaa.44.2021.09.09.16.33.31; Thu, 09 Sep 2021 16:33:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347511AbhIIW6E (ORCPT + 99 others); Thu, 9 Sep 2021 18:58:04 -0400 Received: from mga14.intel.com ([192.55.52.115]:38575 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244256AbhIIW6E (ORCPT ); Thu, 9 Sep 2021 18:58:04 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10102"; a="220610022" X-IronPort-AV: E=Sophos;i="5.85,281,1624345200"; d="scan'208";a="220610022" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2021 15:56:53 -0700 X-IronPort-AV: E=Sophos;i="5.85,281,1624345200"; d="scan'208";a="694374571" Received: from akleen-mobl1.amr.corp.intel.com (HELO [10.212.200.87]) ([10.212.200.87]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2021 15:56:52 -0700 Subject: Re: [PATCH v2] perf list: Display hybrid pmu events with cpu type To: Ian Rogers , Jin Yao Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, kan.liang@intel.com, yao.jin@intel.com References: <20210903025239.22754-1-yao.jin@linux.intel.com> From: Andi Kleen Message-ID: <0ccb62bf-34be-b986-4794-d8cc2a767a3e@linux.intel.com> Date: Thu, 9 Sep 2021 15:56:51 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/9/2021 3:37 PM, Ian Rogers wrote: > On Thu, Sep 2, 2021 at 7:54 PM Jin Yao wrote: >> Add a new option '--cputype' to perf-list to display core-only pmu events >> or atom-only pmu events. >> >> Each hybrid pmu event has been assigned with a pmu name, this patch >> compares the pmu name before listing the result. > Would this work more broadly for any PMU type? If so perhaps pmu > rather than cputype is a more appropriate option name? It's not just the cpu pmu, because it still lists the uncore events, which makes sense. If you want to match the pmu it probably would make sense to match it in the default matching for non option arguments in perf list. But that would be a different patch. -Andi