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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CCBF8C54EBD for ; Fri, 13 Jan 2023 04:16:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=99/VrRTZbEsmAETchWs/DG6X5Eq7uCji1DYKx/LQcsc=; b=EAm4TOpch0RRpx ddvH6m7UtxC7XL7X0+5TrU4zGqZICVoWFpJCmhmdnEARHFa0GlMW//SGWIK+5p8YRrY33VhPc7EPt rh8GSNNOB2oKX6p1SRCK1IGh1xp34FzMNvl2n9ZjCE/9u+ymCkltEV+qVWRfIazGh5BMIBxJfnZF0 GxisIdCpbcOnERfwR3y48XPcH+9LtLvkZp27WhKiX/Nk7YmhjxRDiDWdHvF8IUPC7yZQMhY/PXTrZ jLeu8WZHuQYovekdZl6T7mtzVAZx78mLOZ9CFe1UzPXCs2cSeT5y3cdghON46urFMNsClGYqrxk/J btjiV35lfFmynHBKSoZA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pGBTc-000NF3-QP; Fri, 13 Jan 2023 04:15:36 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pGBTY-000NDS-LQ for linux-arm-kernel@lists.infradead.org; Fri, 13 Jan 2023 04:15:34 +0000 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 BD6B2FEC; Thu, 12 Jan 2023 20:16:10 -0800 (PST) Received: from [10.162.41.9] (unknown [10.162.41.9]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8C6133F587; Thu, 12 Jan 2023 20:15:26 -0800 (PST) Message-ID: <0351f0bc-d94b-957f-8e03-6525e47d63a4@arm.com> Date: Fri, 13 Jan 2023 09:45:22 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCH V7 3/6] arm64/perf: Add branch stack support in struct arm_pmu Content-Language: en-US To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Catalin Marinas , Will Deacon References: <20230105031039.207972-1-anshuman.khandual@arm.com> <20230105031039.207972-4-anshuman.khandual@arm.com> From: Anshuman Khandual In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230112_201532_857644_F83FD0E0 X-CRM114-Status: GOOD ( 31.59 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 1/12/23 19:24, Mark Rutland wrote: > On Thu, Jan 05, 2023 at 08:40:36AM +0530, Anshuman Khandual wrote: >> This updates 'struct arm_pmu' for branch stack sampling support later. This >> adds a new 'features' element in the structure to track supported features, >> and another 'private' element to encapsulate implementation attributes on a >> given 'struct arm_pmu'. These updates here will help in tracking any branch >> stack sampling support, which is being added later. This also adds a helper >> arm_pmu_branch_stack_supported(). >> >> This also enables perf branch stack sampling event on all 'struct arm pmu', >> supporting the feature but after removing the current gate that blocks such >> events unconditionally in armpmu_event_init(). Instead a quick probe can be >> initiated via arm_pmu_branch_stack_supported() to ascertain the support. >> >> Cc: Catalin Marinas >> Cc: Will Deacon >> Cc: Mark Rutland >> Cc: linux-arm-kernel@lists.infradead.org >> Cc: linux-kernel@vger.kernel.org >> Signed-off-by: Anshuman Khandual >> --- >> drivers/perf/arm_pmu.c | 3 +-- >> include/linux/perf/arm_pmu.h | 9 +++++++++ >> 2 files changed, 10 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/perf/arm_pmu.c b/drivers/perf/arm_pmu.c >> index 14a3ed3bdb0b..a85b2d67022e 100644 >> --- a/drivers/perf/arm_pmu.c >> +++ b/drivers/perf/arm_pmu.c >> @@ -510,8 +510,7 @@ static int armpmu_event_init(struct perf_event *event) >> !cpumask_test_cpu(event->cpu, &armpmu->supported_cpus)) >> return -ENOENT; >> >> - /* does not support taken branch sampling */ >> - if (has_branch_stack(event)) >> + if (has_branch_stack(event) && !arm_pmu_branch_stack_supported(armpmu)) >> return -EOPNOTSUPP; >> >> return __hw_perf_event_init(event); >> diff --git a/include/linux/perf/arm_pmu.h b/include/linux/perf/arm_pmu.h >> index 2a9d07cee927..64e1b2594025 100644 >> --- a/include/linux/perf/arm_pmu.h >> +++ b/include/linux/perf/arm_pmu.h >> @@ -80,11 +80,14 @@ enum armpmu_attr_groups { >> ARMPMU_NR_ATTR_GROUPS >> }; >> >> +#define ARM_PMU_BRANCH_STACK BIT(0) >> + >> struct arm_pmu { >> struct pmu pmu; >> cpumask_t supported_cpus; >> char *name; >> int pmuver; >> + int features; >> irqreturn_t (*handle_irq)(struct arm_pmu *pmu); >> void (*enable)(struct perf_event *event); >> void (*disable)(struct perf_event *event); > > Hmm, we already have the secure_access field separately. How about we fold that > in and go with: > > unsigned int secure_access : 1, > has_branch_stack : 1; Something like this would work, but should we use __u32 instead of unsigned int to ensure 32 bit width ? - bool secure_access; /* 32-bit ARM only */ + unsigned int secure_access : 1, /* 32-bit ARM only */ + has_branch_stack: 1, + reserved : 31; > > ... that way we have one way to manage flags, we don't need to allocate the > bits, and the bulk of the existing code for secure_access can stay as-is. Right, the changed code also builds on arm32 without any code change. > >> @@ -119,8 +122,14 @@ struct arm_pmu { >> >> /* Only to be used by ACPI probing code */ >> unsigned long acpi_cpuid; >> + void *private; > > Does this need to be on the end of struct arm_pmu, or can it be placed earlier? This additional 'private' attribute structure sticking out from struct arm_pmu should be at the end. But is there any benefit moving this earlier ? > > The line spacing makes it look like the ACPI comment applies to 'private', > which isn't the case. Sure, will add the following comment, and a space in between. diff --git a/include/linux/perf/arm_pmu.h b/include/linux/perf/arm_pmu.h index f60f7e01acae..c0a090ff7991 100644 --- a/include/linux/perf/arm_pmu.h +++ b/include/linux/perf/arm_pmu.h @@ -130,6 +130,8 @@ struct arm_pmu { /* Only to be used by ACPI probing code */ unsigned long acpi_cpuid; + + /* Implementation specific attributes */ void *private; }; > >> }; >> >> +static inline bool arm_pmu_branch_stack_supported(struct arm_pmu *armpmu) >> +{ >> + return armpmu->features & ARM_PMU_BRANCH_STACK; >> +} > > With the above, this would become: > > static inline bool arm_pmu_branch_stack_supported(struct arm_pmu *armpmu) > { > return armpmu->has_branch_stack; > } Right, will change this helper as required. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel