Received: by 2002:a05:6358:7058:b0:131:369:b2a3 with SMTP id 24csp799807rwp; Thu, 13 Jul 2023 00:51:03 -0700 (PDT) X-Google-Smtp-Source: APBJJlGax72zAQwc7klJaALAPI4eaiMi4xMlF92ZiJJK/3fjSqEbyyyhOuwQ86rfXwY9PxvXeL3e X-Received: by 2002:a05:6a20:2594:b0:132:7ae5:46da with SMTP id k20-20020a056a20259400b001327ae546damr855713pzd.53.1689234662920; Thu, 13 Jul 2023 00:51:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689234662; cv=none; d=google.com; s=arc-20160816; b=dp0WW7sjkTzk7vXbV+iIOSNwXr9SGR0sKaLNMfOtegfyNPICOrSkAzvMZPkXQJxptP JLsyUvL0I2quUzo3ro/mBOTgcGCY/H2viq9zGXjGZyEAf/lB4IlEI8flyoe60kzqNPoe PoHt8J465RtV7p18Mkax0HOCgQSCwIxqSjugd440twam/+dh3mNOnfS2JYl8dKR2RG0l M8Nrn7PjGracl1wah35Fw9ZUyps13j4+0PxKdX7B/uipXR4cB74zP1JIndZA/0WW9lP5 YoL/VF+K7dJEFsd0J0KKsBwlbe2PofLqWuMJbHYbmpQhta4f+EyQ9AcFJoQd9v66Wdtu xBaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=/1Auv1JzbXCyvx5lJSamB5WXLK2Zl5XInQK3w1kBMqw=; fh=LH4fM04t0S+m6Gvr8k31rpsg0SOSoJXPoKbSw1qfGJA=; b=CcksKJ9N1hFgMe0nAbd711LExdsVIQQ3TJ98DyxWpWa79obMYGX7V0ZxSf+vz549gw TmTbH643O9axE4U6C2weC1XntBakQmG3PWBQHeafIs+GfGXQZJ9m2a2sJDaNIgirH6Pq rVHQJieD7gdNvXzd46uHQ//OPZoQD89faLCC05dprMTqvoJ4aTOh8jvAvwm4fR5VNLN/ UThESbaCW6RrwGTtTy90t36xuGbkypWWc0FeE4QQL77g8a0DdT/56kzqPjy6rorFgrGu wQ/CvJXDtyGNB9ZT9XgLDHuYhKOQ0IYiEuejbL75tmeQngyKw4FnL5HbcwO/NZLUpedb SRuA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u189-20020a6385c6000000b005539899e4cdsi4824855pgd.813.2023.07.13.00.50.50; Thu, 13 Jul 2023 00:51:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234147AbjGMHbH (ORCPT + 99 others); Thu, 13 Jul 2023 03:31:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51890 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233486AbjGMHbG (ORCPT ); Thu, 13 Jul 2023 03:31:06 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B50D9E77; Thu, 13 Jul 2023 00:31:04 -0700 (PDT) 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 E4E821570; Thu, 13 Jul 2023 00:31:46 -0700 (PDT) Received: from [10.163.49.144] (unknown [10.163.49.144]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 44FD03F73F; Thu, 13 Jul 2023 00:30:57 -0700 (PDT) Message-ID: Date: Thu, 13 Jul 2023 13:00:55 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH 4/4] perf: Remove unused PERF_PMU_CAP_HETEROGENEOUS_CPUS capability Content-Language: en-US To: James Clark Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Adrian Hunter , Thomas Gleixner , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Will Deacon , Kan Liang , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-perf-users@vger.kernel.org, irogers@google.com References: <20230710122138.1450930-1-james.clark@arm.com> <20230710122138.1450930-5-james.clark@arm.com> <96a3d12a-71d8-1779-28a3-316e1838292e@arm.com> <6143e1cd-4db7-d980-a189-b9b06f99d7c4@arm.com> From: Anshuman Khandual In-Reply-To: <6143e1cd-4db7-d980-a189-b9b06f99d7c4@arm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/11/23 19:45, James Clark wrote: > > > On 11/07/2023 13:10, Anshuman Khandual wrote: >> >> >> On 7/10/23 17:51, James Clark wrote: >>> Since commit bd2756811766 ("perf: Rewrite core context handling") the >>> relationship between perf_event_context and PMUs has changed so that >>> the error scenario that PERF_PMU_CAP_HETEROGENEOUS_CPUS originally >>> silenced no longer exists. >>> >>> Remove the capability to avoid confusion that it actually influences >>> any perf core behavior. This change should be a no-op. >>> >>> Signed-off-by: James Clark >>> --- >>> include/linux/perf_event.h | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h >>> index d5628a7b5eaa..3f4d941fd6c5 100644 >>> --- a/include/linux/perf_event.h >>> +++ b/include/linux/perf_event.h >>> @@ -288,7 +288,7 @@ struct perf_event_pmu_context; >>> #define PERF_PMU_CAP_EXTENDED_REGS 0x0008 >>> #define PERF_PMU_CAP_EXCLUSIVE 0x0010 >>> #define PERF_PMU_CAP_ITRACE 0x0020 >>> -#define PERF_PMU_CAP_HETEROGENEOUS_CPUS 0x0040 >>> +/* Unused 0x0040 */ >> >> Small nit, "Unused" marking might not be required here. >> > > But then it would be very easy to miss that there is a free bit if I > don't leave the comment. Is it really better without it? > > I could shift all the following ones down by one bit, but it would be a Sounds as a better option IMHO. > lot of work to make sure that nobody has hard coded some check for one > of the bits instead of using the define somewhere. These are not user visible ABI and hence defined in include/linux/perf_event.h to be used by drivers registering a PMU for capability enumeration. I am just wondering why they might have been hard coded any where ? > >>> #define PERF_PMU_CAP_NO_EXCLUDE 0x0080 >>> #define PERF_PMU_CAP_AUX_OUTPUT 0x0100 >>> #define PERF_PMU_CAP_EXTENDED_HW_TYPE 0x0200