Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp895673rwl; Wed, 12 Apr 2023 05:47:26 -0700 (PDT) X-Google-Smtp-Source: AKy350Y3/EsUPGdFvD2QTWkVyxhUUrSjiosCq9hGQyFpAhL4gQQeJpgmN3E66ILGm/r+86j/MMV8 X-Received: by 2002:a17:906:8a5b:b0:94d:8b66:46d1 with SMTP id gx27-20020a1709068a5b00b0094d8b6646d1mr1756496ejc.6.1681303645812; Wed, 12 Apr 2023 05:47:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681303645; cv=none; d=google.com; s=arc-20160816; b=K3k285MDaBK21S7KbOmZNEDo+n445Bq6pw90ykQ78MzZZXGJQ+XBDLC6APMNqJauEu G6f+l1lb/O+KQrg977Iyn97wFjv5M4350kbPSIZSxcMBUYbtd6s4cCY0bRrAEvs7zQzn DEysGYOQJTZHhn4zk08g1OHobc3alTTn5SyEtAIvonbbPwPvK8E0+gj3q22c1dpLKx+i wMn/tZ7RobtR6uNp4h/8M4UtQv8F1SSVl2UdFjt03YTK1qdycrwVYBT3ancrEhGD5k/4 P4DlDYpcpHupbsDJVPmDZbsgvWfi+GywteSaCbw3rpqmoDb/9vycz8clUQLB6wrgfzrC 09ig== 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=LfqjoKLxUqVowsP40WJWwBY0P4w/D1VEG9R56JFsIEI=; b=nL0nNOeWYSTUxkbfbdgVJMoyr3lfzGwzblX3iPWkMg+xzSnztrDaNOSINF9+WnJhJb XyLtxZUmplqa1uFdvGKwLGjqMQu5cUcjlirm+BUb31Yil2x7chpoSAc+cHsMm5QVQNS2 8Q/McEgNmbkdOZjMVo2HWZwrCJrDaAbkfG8+2R5JH118aYMGE2btusGhUFI2MAV3+UXA 05lFg0J2SK2XNF2sBf7dRR3ns4+OKbK5WGp5X3w6redkrBHnWtj04vv0xt+beCohtJKE LpPPzUSscyLZw5QLVo8mfkjPYmtN4S/MQAZvuUpTYSesyNk+enqPm0CJusUDl6jaKXuJ p9Gg== 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 tx17-20020a1709078e9100b0094a65b0e9d1si8340379ejc.375.2023.04.12.05.47.01; Wed, 12 Apr 2023 05:47:25 -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 S230328AbjDLMlo (ORCPT + 99 others); Wed, 12 Apr 2023 08:41:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbjDLMll (ORCPT ); Wed, 12 Apr 2023 08:41:41 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id E929646B1; Wed, 12 Apr 2023 05:41:34 -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 0FB8FD75; Wed, 12 Apr 2023 05:42:19 -0700 (PDT) Received: from [10.57.55.240] (unknown [10.57.55.240]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 422CA3F73F; Wed, 12 Apr 2023 05:41:29 -0700 (PDT) Message-ID: <71167f33-1e54-53ed-0101-c7293149d89b@arm.com> Date: Wed, 12 Apr 2023 13:41:27 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [PATCH 01/32] perf: Allow a PMU to have a parent Content-Language: en-GB To: Jonathan Cameron , Peter Zijlstra Cc: Yicong Yang , Mark Rutland , Ingo Molnar , Arnaldo Carvalho de Melo , Will Deacon , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org, yangyicong@hisilicon.com, linuxarm@huawei.com, Dan Williams , Shaokun Zhang , Jiucheng Xu , Khuong Dinh , Robert Richter , Atish Patra , Anup Patel , Andy Gross , Bjorn Andersson , Frank Li , Shuai Xue , Vineet Gupta , Shawn Guo , Fenghua Yu , Dave Jiang , Wu Hao , Tom Rix , linux-fpga@vger.kernel.org, Suzuki K Poulose , Liang Kan References: <20230404134225.13408-1-Jonathan.Cameron@huawei.com> <20230404134225.13408-2-Jonathan.Cameron@huawei.com> <61f8e489-ae76-38d6-2da0-43cf3c17853d@huawei.com> <20230406111607.00007be5@Huawei.com> <20230406124040.GD392176@hirez.programming.kicks-ass.net> <20230406174445.0000235c@Huawei.com> From: Robin Murphy In-Reply-To: <20230406174445.0000235c@Huawei.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE 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 2023-04-06 17:44, Jonathan Cameron wrote: > On Thu, 6 Apr 2023 14:40:40 +0200 > Peter Zijlstra wrote: > >> On Thu, Apr 06, 2023 at 11:16:07AM +0100, Jonathan Cameron wrote: >> >>> In the long run I agree it would be good. Short term there are more instances of >>> struct pmu that don't have parents than those that do (even after this series). >>> We need to figure out what to do about those before adding checks on it being >>> set. >> >> Right, I don't think you've touched *any* of the x86 PMUs for example, >> and getting everybody that boots an x86 kernel a warning isn't going to >> go over well :-) >> > > It was tempting :) "Warning: Parentless PMU: try a different architecture." > > I'd love some inputs on what the x86 PMU devices parents should be? > CPU counters in general tend to just spin out of deep in the architecture code. > > My overall favorite is an l2 cache related PMU that is spun up in > arch/arm/kernel/irq.c init_IRQ() > > I'm just not going to try and figure out why... I think that's simply because the PMU support was hung off the existing PL310 configuration code, which still supports non-DT boardfiles. The PMU shouldn't strictly need to be registered that early, it would just be a bunch more work to ensure that a platform device is available for it to bind to as a regular driver model driver, which wasn't justifiable at the time. Thanks, Robin.