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 X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6DFBC3A5A1 for ; Thu, 22 Aug 2019 16:40:29 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 86E362133F for ; Thu, 22 Aug 2019 16:40:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GeEb9Mkn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 86E362133F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=lWtM+KjI3whrpOzYE6xyaKcjRG4K546cG1qdKrOiK/Y=; b=GeEb9MknkhPFKr 969J1F9kIKytxzNDG8SwJn68QOP7wjXYOcR/QXQUboeg2f9LJjRUSpsRXUq3zeVbiwOhyvO7mJhJ0 xHJ80bCgyc31eBe0eMytlz5Kuk20u6czWb4Z0jeqaS8o/GFAQmHdF08oMFPVmTkzLBv6DuLRZnPto 9CwwrhKZsdJ67/8nIjJoIj0OQ0F3g0ZVtiS4Lb4cyPOZBbFttpQIKn1lrFNTK+OJelxV7gBsFo3Qn PoF3bPy5ObP9VzogYDqnxY6aaiEq+/grl2qYRUuri0hsRWUienIzfzDkKRqRsRrzuVOXQe1taq5in h9yoHQNfQutDyMLqqvCQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1i0q8M-0000Fd-4W; Thu, 22 Aug 2019 16:40:22 +0000 Received: from szxga05-in.huawei.com ([45.249.212.191] helo=huawei.com) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1i0q8I-0008NC-7e for linux-arm-kernel@lists.infradead.org; Thu, 22 Aug 2019 16:40:20 +0000 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id A2FF76325640AF5DDC2F; Fri, 23 Aug 2019 00:40:01 +0800 (CST) Received: from localhost (10.227.98.71) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.439.0; Fri, 23 Aug 2019 00:39:56 +0800 Date: Fri, 23 Aug 2019 00:39:45 +0800 From: Jonathan Cameron To: Raphael Gault Subject: Re: [PATCH v4 6/7] arm64: perf: Enable pmu counter direct access for perf event on armv8 Message-ID: <20190823003945.00004a69@huawei.com> In-Reply-To: <20190822144220.27860-7-raphael.gault@arm.com> References: <20190822144220.27860-1-raphael.gault@arm.com> <20190822144220.27860-7-raphael.gault@arm.com> Organization: Huawei R&D UK Ltd. X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 X-Originating-IP: [10.227.98.71] X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190822_094018_471657_9E35C954 X-CRM114-Status: GOOD ( 20.15 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: mark.rutland@arm.com, raph.gault+kdev@gmail.com, peterz@infradead.org, catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, acme@kernel.org, mingo@redhat.com, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 22 Aug 2019 15:42:19 +0100 Raphael Gault wrote: > Keep track of event opened with direct access to the hardware counters > and modify permissions while they are open. > > The strategy used here is the same which x86 uses: everytime an event > is mapped, the permissions are set if required. The atomic field added > in the mm_context helps keep track of the different event opened and > de-activate the permissions when all are unmapped. > We also need to update the permissions in the context switch code so > that tasks keep the right permissions. > > Signed-off-by: Raphael Gault Hi Raphael, One trivial comment inline. Thanks, Jonathan > --- > arch/arm64/include/asm/mmu.h | 6 ++++ > arch/arm64/include/asm/mmu_context.h | 2 ++ > arch/arm64/include/asm/perf_event.h | 14 ++++++++ > arch/arm64/kernel/perf_event.c | 1 + > drivers/perf/arm_pmu.c | 54 ++++++++++++++++++++++++++++ > 5 files changed, 77 insertions(+) > > diff --git a/arch/arm64/include/asm/mmu.h b/arch/arm64/include/asm/mmu.h > index fd6161336653..88ed4466bd06 100644 > --- a/arch/arm64/include/asm/mmu.h > +++ b/arch/arm64/include/asm/mmu.h > @@ -18,6 +18,12 @@ > > typedef struct { > atomic64_t id; > + > + /* > + * non-zero if userspace have access to hardware > + * counters directly. > + */ > + atomic_t pmu_direct_access; > void *vdso; > unsigned long flags; > } mm_context_t; > diff --git a/arch/arm64/include/asm/mmu_context.h b/arch/arm64/include/asm/mmu_context.h > index 7ed0adb187a8..6e66ff940494 100644 > --- a/arch/arm64/include/asm/mmu_context.h > +++ b/arch/arm64/include/asm/mmu_context.h > @@ -21,6 +21,7 @@ > #include > #include > #include > +#include > #include > #include > > @@ -224,6 +225,7 @@ static inline void __switch_mm(struct mm_struct *next) > } > > check_and_switch_context(next, cpu); > + perf_switch_user_access(next); > } > > static inline void > diff --git a/arch/arm64/include/asm/perf_event.h b/arch/arm64/include/asm/perf_event.h > index 2bdbc79bbd01..ba58fa726631 100644 > --- a/arch/arm64/include/asm/perf_event.h > +++ b/arch/arm64/include/asm/perf_event.h > @@ -8,6 +8,7 @@ > > #include > #include > +#include > > #define ARMV8_PMU_MAX_COUNTERS 32 > #define ARMV8_PMU_COUNTER_MASK (ARMV8_PMU_MAX_COUNTERS - 1) > @@ -223,4 +224,17 @@ extern unsigned long perf_misc_flags(struct pt_regs *regs); > (regs)->pstate = PSR_MODE_EL1h; \ > } > > +static inline void perf_switch_user_access(struct mm_struct *mm) > +{ > + if (!IS_ENABLED(CONFIG_PERF_EVENTS)) > + return; > + > + if (atomic_read(&mm->context.pmu_direct_access)) { > + write_sysreg(ARMV8_PMU_USERENR_ER|ARMV8_PMU_USERENR_CR, > + pmuserenr_el0); > + } else { > + write_sysreg(0, pmuserenr_el0); > + } > +} > + > #endif > diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c > index de9b001e8b7c..7de56f22d038 100644 > --- a/arch/arm64/kernel/perf_event.c > +++ b/arch/arm64/kernel/perf_event.c > @@ -1285,6 +1285,7 @@ void arch_perf_update_userpage(struct perf_event *event, > */ > freq = arch_timer_get_rate(); > userpg->cap_user_time = 1; > + userpg->cap_user_rdpmc = !!(event->hw.flags & ARMPMU_EL0_RD_CNTR); > > clocks_calc_mult_shift(&userpg->time_mult, &shift, freq, > NSEC_PER_SEC, 0); > diff --git a/drivers/perf/arm_pmu.c b/drivers/perf/arm_pmu.c > index 2d06b8095a19..d0d3e523a4c4 100644 > --- a/drivers/perf/arm_pmu.c > +++ b/drivers/perf/arm_pmu.c > @@ -25,6 +25,7 @@ > #include > > #include > +#include > > static DEFINE_PER_CPU(struct arm_pmu *, cpu_armpmu); > static DEFINE_PER_CPU(int, cpu_irq); > @@ -778,6 +779,57 @@ static void cpu_pmu_destroy(struct arm_pmu *cpu_pmu) > &cpu_pmu->node); > } > > +static void refresh_pmuserenr(void *mm) > +{ > + perf_switch_user_access(mm); > +} > + > +static int check_homogeneous_cap(struct perf_event *event, struct mm_struct *mm) > +{ > + pr_info("checking HAS_HOMOGENEOUS_PMU"); Can we drop this spam from the good path. Makes a bit of a mess of my terminal when running the test ;) > + if (!cpus_have_cap(ARM64_HAS_HOMOGENEOUS_PMU)) { > + pr_info("Disable direct access (!HAS_HOMOGENEOUS_PMU)"); > + atomic_set(&mm->context.pmu_direct_access, 0); > + on_each_cpu(refresh_pmuserenr, mm, 1); > + event->hw.flags &= ~ARMPMU_EL0_RD_CNTR; > + return 0; > + } > + > + return 1; > +} > + > +static void armpmu_event_mapped(struct perf_event *event, struct mm_struct *mm) > +{ > + if (!(event->hw.flags & ARMPMU_EL0_RD_CNTR)) > + return; > + > + /* > + * This function relies on not being called concurrently in two > + * tasks in the same mm. Otherwise one task could observe > + * pmu_direct_access > 1 and return all the way back to > + * userspace with user access disabled while another task is still > + * doing on_each_cpu_mask() to enable user access. > + * > + * For now, this can't happen because all callers hold mmap_sem > + * for write. If this changes, we'll need a different solution. > + */ > + lockdep_assert_held_write(&mm->mmap_sem); > + > + if (check_homogeneous_cap(event, mm) && > + atomic_inc_return(&mm->context.pmu_direct_access) == 1) > + on_each_cpu(refresh_pmuserenr, mm, 1); > +} > + > +static void armpmu_event_unmapped(struct perf_event *event, struct mm_struct *mm) > +{ > + if (!(event->hw.flags & ARMPMU_EL0_RD_CNTR)) > + return; > + > + if (check_homogeneous_cap(event, mm) && > + atomic_dec_and_test(&mm->context.pmu_direct_access)) > + on_each_cpu_mask(mm_cpumask(mm), refresh_pmuserenr, NULL, 1); > +} > + > static struct arm_pmu *__armpmu_alloc(gfp_t flags) > { > struct arm_pmu *pmu; > @@ -799,6 +851,8 @@ static struct arm_pmu *__armpmu_alloc(gfp_t flags) > .pmu_enable = armpmu_enable, > .pmu_disable = armpmu_disable, > .event_init = armpmu_event_init, > + .event_mapped = armpmu_event_mapped, > + .event_unmapped = armpmu_event_unmapped, > .add = armpmu_add, > .del = armpmu_del, > .start = armpmu_start, _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel