Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp600268pxy; Fri, 30 Apr 2021 12:01:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxLl8Y85T8Q+PZV9mG40O99qVRSn69A5hNO3l+3bHwt4YSbgAXxb/MGwnHLxcjDdpW5nLKt X-Received: by 2002:a17:90b:1bc1:: with SMTP id oa1mr6438773pjb.46.1619809288221; Fri, 30 Apr 2021 12:01:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619809288; cv=none; d=google.com; s=arc-20160816; b=rnhmkuus7d+/BhdRBqBYtu9TyZT094Sn5orKXISRcrzcMpAXmuBIyZl3uglu/9gx81 BKps4qgE2fVqPj795D90fEjtqZgQhIlz5+NXvYmonkF831gdL+8rwQBAj+9weyqJJXbY HH6pHo4SAauGGM2cG9yZeuk0DepqE+QjwfK4uomvQOO4dr/ZHvVLza57lsbiT7Pqd+xc V/ALL2TMhlm0jAW6hUi73g7vdcyLYi2OpOEquZU8GCUbtGgXkd/sjQN6hq9PdGX8+Bwi Whh2LJ6A9mVdIMpgdzmRL2w2Qefbml4/j4xA/GxW4WSCN96avc1ahe1XzHFkG8aFLo+3 ezYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=HVP66b3ji+SY6LoaFRFDWOgfmWhYM2kleQ+7MzfplD0=; b=d4b9dI0eCF5tBAnVh4pFsA8SkJvahORA6ah/5x+LDZWm77dySNqUO/IaGQcp6B4JDS vxPCcE9r6ZlgtJ8yIKdn0h8S9TLkbeuusWydKF8dpluSQhRHNFoCVtc+YIxYjctongCL BWDmY1EPzBdyZPMWnmi1WMKU086qp5N9Q6iSVp37G9l1AJZZh3OMrM8nMCps+Y2mAdFI BcmEw1aAg2Siu60QB4DV40NBGzLz/fSDGtTGMBhuVWdjJg3s7l263sZK+dB7I9vzMYYd P5d9tF3g2HhYaILUFuNd6UFjINlyZZXhdCrnUKUMAD+igPg8znsktbSVbiOcMQ7tqbps nAQA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=MT8Qzi9w; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i26si4364098pgl.346.2021.04.30.12.01.13; Fri, 30 Apr 2021 12:01:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=MT8Qzi9w; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231719AbhD3TAA (ORCPT + 99 others); Fri, 30 Apr 2021 15:00:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:58028 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231136AbhD3TAA (ORCPT ); Fri, 30 Apr 2021 15:00:00 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id D3CFE60233; Fri, 30 Apr 2021 18:59:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1619809151; bh=iLa54GJRd4w9lzNeN2FcvEnXnhXHBcTHxM2aqsdDVlo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MT8Qzi9wVH4Ixu3E8GU76/pxIz7iNSV4K9qkF0owrMA9q/Yw23s4du1l4MkW+EHxQ yADaSCMiNnb4EaYH9dKF98g+VtgitNuQVJYchEPNe59rRGER7mq2jriwfGe26JWmXD YWHAzk3LsIDZg7W2SpwFQCe8HGZI5h4tF6a74qHKy+GoE30xbOzy+6PB3GGhGK1ZL4 b94v2XrPGmgHS6Ad687aaezw7i8loQxiPq1RaVGqltCWASvpRKKfiHlDbFlFiPuubG HX1r0L8FkKAj06dvgikinm0rEo6SHpmXjgsFbTwq12v6Dqu63t3+yzx0fYtOx0PxdB tVwZdad4Cyd+w== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id 7021A4034C; Fri, 30 Apr 2021 15:59:08 -0300 (-03) Date: Fri, 30 Apr 2021 15:59:08 -0300 From: Arnaldo Carvalho de Melo To: Rob Herring Cc: Will Deacon , Catalin Marinas , Peter Zijlstra , Ingo Molnar , Jiri Olsa , Mark Rutland , Alexander Shishkin , honnappa.nagarahalli@arm.com, Zachary.Leaf@arm.com, Raphael Gault , Jonathan Cameron , Namhyung Kim , Itaru Kitayama , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 0/9] arm64 userspace counter access support Message-ID: References: <20210420031511.2348977-1-robh@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210420031511.2348977-1-robh@kernel.org> X-Url: http://acmel.wordpress.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Mon, Apr 19, 2021 at 10:15:02PM -0500, Rob Herring escreveu: > Hi all, > > Another version of arm64 userspace counter access support. I sent out > the libperf bits separately and those are now applied (Thanks!), so this > is just the arm64 bits. > > > This originally resurrected Raphael's series[1] to enable userspace counter > access on arm64. My previous versions are here[2][3][4][5][6][7]. A git > branch is here[8]. Rob, please don't mix kernel patches with tools patches. The kernel bits, if arch specific should go via the arch maintainer, core stuff to PeterZ/Ingo/bpetkov/tglx, and tooling stuff I'll collect. We did it on purpose to avoid any semblance of kernel/tool lockstep. The kernel changes should not prevent the tooling from working and the tooling changes shouldn't require the kernel changes. Preexisting kernels should work with new tools and vice versa. Thanks, - Arnaldo > > Changes in v7: > - Handling of dirty counter leakage and reworking of context switch and > user access enabling. The .sched_task hook and undef instruction handler > are now utilized. (Patch 3) > - Add a userspace disable switch like x86. (Patch 5) > > Changes in v6: > - Reworking of the handling of 64-bit counters and user access. There's > a new config1 flag to request user access. This takes priority over > the 64-bit flag and the user will get the maximum size the h/w > supports without chaining. > - The libperf evsel mmap struct is stored in its own xyarray > - New tests for user 64-bit and 32-bit counters > - Rebase to v5.12-rc2 > > Changes in v5: > - Limit enabling/disabling access to CPUs associated with the PMU > (supported_cpus) and with the mm_struct matching current->active_mm. > The x86 method of using mm_cpumask doesn't work for arm64 as it is not > updated. > - Only set cap_user_rdpmc if event is on current cpu. See patch 2. > - Create an mmap for every event in an evsel. This results in some changes > to the libperf mmap API from the last version. > - Rebase to v5.11-rc2 > > Changes in v4: > - Dropped 'arm64: pmu: Add hook to handle pmu-related undefined instructions'. > The onus is on userspace to pin itself to a homogeneous subset of CPUs > and avoid any aborts on heterogeneous systems, so the hook is not needed. > - Make perf_evsel__mmap() take pages rather than bytes for size > - Fix building arm64 heterogeneous test. > > Changes in v3: > - Dropped removing x86 rdpmc test until libperf tests can run via 'perf test' > - Added verbose prints for tests > - Split adding perf_evsel__mmap() to separate patch > > The following changes to the arm64 support have been made compared to > Raphael's last version: > > The major change is support for heterogeneous systems with some > restrictions. Specifically, userspace must pin itself to like CPUs, open > a specific PMU by type, and use h/w specific events. The tests have been > reworked to demonstrate this. > > Chained events are not supported. The problem with supporting chained > events was there's no way to distinguish between a chained event and a > native 64-bit counter. We could add some flag, but do self monitoring > processes really need that? Native 64-bit counters are supported if the > PMU h/w has support. As there's already an explicit ABI to request 64-bit > counters, userspace can request 64-bit counters and if user > access is not enabled, then it must retry with 32-bit counters. > > Prior versions broke the build on arm32 (surprisingly never caught by > 0-day). As a result, event_mapped and event_unmapped implementations have > been moved into the arm64 code. > > There was a bug in that pmc_width was not set in the user page. The tests > now check for this. > > The documentation has been converted to rST. I've added sections on > chained events and heterogeneous. > > The tests have been expanded to test the cycle counter access. > > Rob > > [1] https://lore.kernel.org/r/20190822144220.27860-1-raphael.gault@arm.com/ > [2] https://lore.kernel.org/r/20200707205333.624938-1-robh@kernel.org/ > [3] https://lore.kernel.org/r/20200828205614.3391252-1-robh@kernel.org/ > [4] https://lore.kernel.org/r/20200911215118.2887710-1-robh@kernel.org/ > [5] https://lore.kernel.org/r/20201001140116.651970-1-robh@kernel.org/ > [6] https://lore.kernel.org/r/20210114020605.3943992-1-robh@kernel.org/ > [7] https://lore.kernel.org/r/20210311000837.3630499-1-robh@kernel.org/ > [8] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git user-perf-event-v7 > > Raphael Gault (4): > arm64: Restrict undef hook for cpufeature registers > arm64: pmu: Add function implementation to update event index in > userpage > arm64: perf: Enable PMU counter direct access for perf event > Documentation: arm64: Document PMU counters access from userspace > > Rob Herring (5): > drivers/perf: arm_pmu: Export the per_cpu cpu_armpmu > arm64: perf: Add userspace counter access disable switch > libperf: Add arm64 support to perf_mmap__read_self() > perf: arm64: Add test for userspace counter access on heterogeneous > systems > perf: arm64: Add tests for 32-bit and 64-bit counter size userspace > access > > Documentation/arm64/perf.rst | 67 +++++- > arch/arm64/include/asm/mmu.h | 5 + > arch/arm64/kernel/cpufeature.c | 4 +- > arch/arm64/kernel/perf_event.c | 254 ++++++++++++++++++++- > drivers/perf/arm_pmu.c | 2 +- > include/linux/perf/arm_pmu.h | 14 +- > tools/lib/perf/mmap.c | 98 ++++++++ > tools/lib/perf/tests/test-evsel.c | 2 +- > tools/perf/arch/arm64/include/arch-tests.h | 12 + > tools/perf/arch/arm64/tests/Build | 1 + > tools/perf/arch/arm64/tests/arch-tests.c | 12 + > tools/perf/arch/arm64/tests/user-events.c | 215 +++++++++++++++++ > 12 files changed, 672 insertions(+), 14 deletions(-) > create mode 100644 tools/perf/arch/arm64/tests/user-events.c > > -- > 2.27.0 -- - Arnaldo