From patchwork Fri Oct 12 15:46:29 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Will Deacon X-Patchwork-Id: 10638821 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id ABF34933 for ; Fri, 12 Oct 2018 15:47:12 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 99D652C0E0 for ; Fri, 12 Oct 2018 15:47:12 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 8DF902C0F3; Fri, 12 Oct 2018 15:47:12 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 371A52C0E0 for ; Fri, 12 Oct 2018 15:47:12 +0000 (UTC) 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: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:In-Reply-To:References: List-Owner; bh=18BpOKJEDzDYC1ynLrvuDcO3n9UPYQ+U5uNKYxuMVYc=; b=nXWRULSg8RAx6P nYY3FGXImnzmBnCKuD6VOfgL+Bh9Q1u07JL77let+4ip2DHJWByDloH6WPcI/swKq/D6DV2QPQHva q1jQHHxxjBIhpBS5M3mpZvBvEVs0mo4ROKTJ7Ff+fKHUx4vuRioCWK6ieHPrHznF8DWQjq96Oxy6R uiVvhjx0qb4uwdzLVaJm+WRAQDa15QvnoaSm9mr3AMRFl7O0onk5i0I5PYo4TznPSulQna1Eedc2P Np4qDk4l+GQQU6ytQonmMEqAJ1gjKT2m11Wj6qavoB4o88PtwvMoRPfK4PT2VRj1CvjzvhjcJoeKG q5RcxIcjQsSJyYnNz2Xg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gAzeY-0000Am-RB; Fri, 12 Oct 2018 15:47:02 +0000 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70] helo=foss.arm.com) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gAzeB-00005F-EN for linux-arm-kernel@lists.infradead.org; Fri, 12 Oct 2018 15:46:59 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 12B01F; Fri, 12 Oct 2018 08:46:29 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id D90D93F5BC; Fri, 12 Oct 2018 08:46:28 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id 57A0F1AE09F2; Fri, 12 Oct 2018 16:46:29 +0100 (BST) Date: Fri, 12 Oct 2018 16:46:29 +0100 From: Will Deacon To: gregkh@linuxfoundation.org Subject: [GIT PULL] Couple more arm64 fixes for 4.19 Message-ID: <20181012154629.GB11387@arm.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20181012_084639_524179_AF46FC99 X-CRM114-Status: GOOD ( 15.08 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: catalin.marinas@arm.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org X-Virus-Scanned: ClamAV using ClamSMTP Hi Greg, Please pull these two arm64 fixes for 4.19. One of them fixes a nasty WARN() that has started triggering because we assumed that memory reservations from firmware would always correspond to regions of the physical address space that we have mapped as memory. Unfortunately, some existing device-tree files break this assumption and we need to continue supporting them. The other fix addresses an issue where a CHAIN PMU event can be requested as a 32-bit counter via perf, which makes no sense in isolation since these events are intended to be used in conjunction with another event when creating a 64-bit counter. This is summarised in the tag. Cheers, Will --->8 The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21: Linux 4.19-rc7 (2018-10-07 17:26:02 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes for you to fetch changes up to ca2b497253ad01c80061a1f3ee9eb91b5d54a849: arm64: perf: Reject stand-alone CHAIN events for PMUv3 (2018-10-12 15:25:17 +0100) ---------------------------------------------------------------- More arm64 fixes - Reject CHAIN PMU events when they are not part of a 64-bit counter - Fix WARN_ON_ONCE() that triggers for reserved regions that don't correspond to mapped memory ---------------------------------------------------------------- Will Deacon (2): arm64: Fix /proc/iomem for reserved but not memory regions arm64: perf: Reject stand-alone CHAIN events for PMUv3 arch/arm64/kernel/perf_event.c | 7 ++++++ arch/arm64/kernel/setup.c | 56 ++++++++++++++++++++---------------------- drivers/perf/arm_pmu.c | 8 +++++- include/linux/perf/arm_pmu.h | 1 + 4 files changed, 42 insertions(+), 30 deletions(-)