From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756742AbdGLMJQ (ORCPT ); Wed, 12 Jul 2017 08:09:16 -0400 Received: from ozlabs.org ([103.22.144.67]:33775 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756630AbdGLMJP (ORCPT ); Wed, 12 Jul 2017 08:09:15 -0400 From: Michael Ellerman To: Sukadev Bhattiprolu , Arnaldo Carvalho de Melo Cc: Jiri Olsa , Madhavan Srinivasan , Andi Kleen , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, mikey@neuling.org Subject: Re: [GIT PULL] Please pull JSON files for Power9 PMU events In-Reply-To: <20170712020827.GB31223@us.ibm.com> References: <20170712020827.GB31223@us.ibm.com> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Wed, 12 Jul 2017 22:09:12 +1000 Message-ID: <87a849luvr.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sukadev Bhattiprolu writes: > Hi Arnaldo, > > Please pull the JSON files for POWER9 PMU events. > > The following changes since commit 07d306c838c5c30196619baae36107d0615e459b: > > Merge git://www.linux-watchdog.org/linux-watchdog (2017-07-11 09:59:37 -0700) > > are available in the git repository at: > > https://github.com/sukadev/linux/ p9-json > > for you to fetch changes up to f94a86dbb13e18bd7ad566cabe42df63d3bd1039: > > perf vendor events: Add POWER9 PVRs to mapfile (2017-07-11 19:30:40 -0500) > > ---------------------------------------------------------------- > Sukadev Bhattiprolu (2): > perf vendor events: Add POWER9 PMU events > perf vendor events: Add POWER9 PVRs to mapfile I think the PVRs need work. You have: +004e0100,1,power9.json,core +004e0000,1,power9.json,core The first is P9 DD1, but the second doesn't exist. We have it in the kernel, but with a mask of 0xffff0000. From memory the perf code doesn't do any masking or anything fancy, it looks for an exact match. So for starters you should probably drop that one and add 0x004e1200 and 0x004e0200. cheers