Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3986050ybi; Tue, 18 Jun 2019 09:42:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxUis9JfFABxwFyI8Okp7nUv3c08aHyzXeiJwhTi/Uz7DisHFwNn3S45rfhoncj2RlZqsjK X-Received: by 2002:a62:1652:: with SMTP id 79mr57442864pfw.20.1560876157145; Tue, 18 Jun 2019 09:42:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560876157; cv=none; d=google.com; s=arc-20160816; b=Kw2Xe8QwU13CnIS5KxPXim/6THWruDkxvUU0MYIg8EPB4nhROsp+2MrsHH30MotRcF nZ03VYnAV0dAWMijyX4vp9HkUUC244MFO+IiU+SlNKGvhto3mxVyZ0gWLkR8CHa3ySOP EPMwWKVHDxhWCWoeGPdMU+dNm7o9EANjS2NxQF1RWuX4DqhR+0XBRhxA6LfDBfrvpAeD Z3LcK5PJREbNyGhQ7GvwMvoujQCEBBvf5ydFZdRLaJpnMX80uX8wVLznlbzG0fy/OVN5 gkXOrBBvGiOxHovL7j0xbaRS3KtTtO/0FR4MHxN0p9NZwTcqQJxkyZ1sSf1HUrxG99lk 48gw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=iF15e+kHt0vnq9aEAXujh6FDPz5jui2P5PWh+xIPnpA=; b=hvGY2Fnuoob7nLTrGosyrIDZE8BQ8aYOKslEqIg1ctLPaA2CRjVjGZsvoMq1Q3aIQk sdx4E/R9/lmgqI5qsWfdSNA5M9s5pjWwl5IsgJfOHol7vz8SCKWjhjhiFQvWzyCeyAW/ Dg+m0Z4NAlSvMHn89FHBdRrWEKShAN+X1f/Ucc64SaCF26jz2NU8TcT1n0D8awBNblBp qTjbXuQTJirpM1w2Zp+6uYTmC+ZKZ3HP3BH45sYFGV4Zk6fDTJbsDZaIcjX/iAxNj1N0 lJ7nTwrC5og3JSod6NeWEX4HT+ehYQH7ToyeTpNJEAb1nWVd2VMPUNf9yfBCrFWg3Xtx xhMA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q17si12919205pll.285.2019.06.18.09.42.21; Tue, 18 Jun 2019 09:42:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729949AbfFRQmM (ORCPT + 99 others); Tue, 18 Jun 2019 12:42:12 -0400 Received: from foss.arm.com ([217.140.110.172]:49678 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729319AbfFRQmM (ORCPT ); Tue, 18 Jun 2019 12:42:12 -0400 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 8A37F344; Tue, 18 Jun 2019 09:42:11 -0700 (PDT) Received: from fuggles.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3280C3F246; Tue, 18 Jun 2019 09:42:10 -0700 (PDT) Date: Tue, 18 Jun 2019 17:42:08 +0100 From: Will Deacon To: Jeremy Linton Cc: linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, rjw@rjwysocki.net, lenb@kernel.org, mark.rutland@arm.com, lorenzo.pieralisi@arm.com, sudeep.holla@arm.com Subject: Re: [PATCH v4 0/4] arm64: SPE ACPI enablement Message-ID: <20190618164208.GB4270@fuggles.cambridge.arm.com> References: <20190615010910.33921-1-jeremy.linton@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190615010910.33921-1-jeremy.linton@arm.com> User-Agent: Mutt/1.11.1+86 (6f28e57d73f2) () Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 14, 2019 at 08:09:06PM -0500, Jeremy Linton wrote: > This patch series enables the Arm Statistical Profiling > Extension (SPE) on ACPI platforms. > > This is possible because ACPI 6.3 uses a previously > reserved field in the MADT to store the SPE interrupt > number, similarly to how the normal PMU is described. > If a consistent valid interrupt exists across all the > cores in the system, a platform device is registered. > That then triggers the SPE module, which runs as normal. > > We also add the ability to parse the PPTT for IDENTICAL > cores. We then use this to sanity check the single SPE > device we create. This creates a bit of a problem with > respect to the specification though. The specification > says that its legal for multiple tree's to exist in the > PPTT. We handle this fine, but what happens in the > case of multiple tree's is that the lack of a common > node with IDENTICAL set forces us to assume that there > are multiple non-IDENTICAL cores in the machine. > > v3->v4: Rebase to 5.2. > Minor formatting, patch rearrangement. > Add missing `inline` in static header definition. > Drop ARM_SPE_ACPI and just use ARM_SPE_PMU. I'm happy to take this via the arm64 perf tree for 5.3, but I'll need Acks from Raphael on the first two patches and an Ack from Lorenzo on patch 3. Cheers, Will