From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH V7 3/6] arm64/perf: Add branch stack support in struct arm_pmu
Date: Fri, 13 Jan 2023 09:45:22 +0530 [thread overview]
Message-ID: <0351f0bc-d94b-957f-8e03-6525e47d63a4@arm.com> (raw)
In-Reply-To: <Y8ARAjUaE44y+Cw3@FVFF77S0Q05N>
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 <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>> 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
next prev parent reply other threads:[~2023-01-13 4:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 3:10 [PATCH V7 0/6] arm64/perf: Enable branch stack sampling Anshuman Khandual
2023-01-05 3:10 ` [PATCH V7 1/6] drivers: perf: arm_pmu: Add new sched_task() callback Anshuman Khandual
2023-01-05 3:10 ` [PATCH V7 2/6] arm64/perf: Add BRBE registers and fields Anshuman Khandual
2023-01-12 13:24 ` Mark Rutland
2023-01-13 3:02 ` Anshuman Khandual
2023-02-08 19:22 ` Mark Rutland
2023-02-09 5:49 ` Anshuman Khandual
2023-02-09 10:08 ` Mark Rutland
2023-01-05 3:10 ` [PATCH V7 3/6] arm64/perf: Add branch stack support in struct arm_pmu Anshuman Khandual
2023-01-12 13:54 ` Mark Rutland
2023-01-13 4:15 ` Anshuman Khandual [this message]
2023-02-08 19:26 ` Mark Rutland
2023-02-09 3:40 ` Anshuman Khandual
2023-01-05 3:10 ` [PATCH V7 4/6] arm64/perf: Add branch stack support in struct pmu_hw_events Anshuman Khandual
2023-01-12 13:59 ` Mark Rutland
2023-01-05 3:10 ` [PATCH V7 5/6] arm64/perf: Add branch stack support in ARMV8 PMU Anshuman Khandual
2023-01-12 14:29 ` Mark Rutland
2023-01-13 5:11 ` Anshuman Khandual
2023-02-08 19:36 ` Mark Rutland
2023-02-13 8:23 ` Anshuman Khandual
2023-02-23 13:47 ` Mark Rutland
2023-03-06 7:59 ` Anshuman Khandual
2023-01-05 3:10 ` [PATCH V7 6/6] arm64/perf: Enable branch stack events via FEAT_BRBE Anshuman Khandual
2023-01-12 16:51 ` Mark Rutland
2023-01-19 2:48 ` Anshuman Khandual
2023-02-08 20:03 ` Mark Rutland
2023-02-20 8:38 ` Anshuman Khandual
2023-02-23 13:38 ` Mark Rutland
2023-01-06 10:23 ` [PATCH V7 0/6] arm64/perf: Enable branch stack sampling James Clark
2023-01-06 11:13 ` Anshuman Khandual
2023-01-11 5:05 ` Anshuman Khandual
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0351f0bc-d94b-957f-8e03-6525e47d63a4@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox