Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758454AbcJTKhN (ORCPT ); Thu, 20 Oct 2016 06:37:13 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:54996 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754533AbcJTKhM (ORCPT ); Thu, 20 Oct 2016 06:37:12 -0400 Date: Thu, 20 Oct 2016 12:37:07 +0200 From: Peter Zijlstra To: Jan Glauber Cc: Mark Rutland , Will Deacon , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 0/5] Cavium ThunderX uncore PMU support Message-ID: <20161020103707.GB3175@twins.programming.kicks-ass.net> References: <1476955841-27898-1-git-send-email-jglauber@cavium.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1476955841-27898-1-git-send-email-jglauber@cavium.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 432 Lines: 9 On Thu, Oct 20, 2016 at 11:30:36AM +0200, Jan Glauber wrote: > Note: > I'm using perf_sw_context in difference to perf_invalid_context > (see WARN_ON in perf_pmu_register). Reason is that with perf_invalid_context > add() is never called and the counter results are shown as "unsupported" by > perf. With perf_sw_context everything works as expected. What?! All the uncore PMUs use perf_invalid_context. What doesn't work for you?