Received: by 10.213.65.68 with SMTP id h4csp1233028imn; Wed, 14 Mar 2018 13:44:10 -0700 (PDT) X-Google-Smtp-Source: AG47ELsEtiNeYoj+KtzJ9aqNmkq52mV63AQwmRsnPY3M+bfeZ4GA+LzrWX+xMOwhAiKlbfwRXBDm X-Received: by 10.101.89.6 with SMTP id f6mr4700028pgu.178.1521060250413; Wed, 14 Mar 2018 13:44:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521060250; cv=none; d=google.com; s=arc-20160816; b=heiR0OA+nBWqfN54yMNHtnMPKpQ72QEWe54hd+KXU7OS5Fl3ZhYfI/yru44M8m4AZj IvlVZARCy4Mmy2sHky8DTXVC6t6FbXMaguZqb91tPjrQxx8DY9hr8PFNwFqWXdSyh0Yo 35nC3ulE2DxkUMvHNSjIDfNbNWJj9g7InmuDkq+hG8Pgg5M7m1z2Fas9oCvrxIvL/Zcx P3+Gp5tIfWTEvYBg//UGwu1rLO4VMX6JWDiL5MSn0aoiArTrFLR2SylvBlUF7WLqpn21 NNZ18t9A3WrN6BZdppHMw8Y3jLBaOuAFPRT7NOTm2g+K/6U6f++ZxvbIeZq9VgUeEBQO m8DA== 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:dmarc-filter:arc-authentication-results; bh=Pgd6Mcw19OeaAWTnfrXf04L+ZPsKTao1RQiKdvtLwUA=; b=jav4DZUG7S0hghc5GUcEdaFGFk0Zrfiuur3uAawYeIZ3PHM5tIgACnidaI0LRGH9bX VXHqcLF4t/c+l96jP+03dKpv28pebZ1f4NK16tnResSSX2hBufJIojcoC4r0obB65+Sv 6Zd7m75wkslF6MO0TFumNSB12S3B+WzrcxhcFDX+snknD+L/Zv1nNqnw/fudds7cJoKO Ays+GA86HtoagsGBYmyUkIk9r7jh6pGF36tHjH2B8ytgsg+x6anM9pyAZEhhD0ZIjF/m rfPrHPPswB22QaQ4giLC5wH5cw/EFheu5S8pZavP/pl/r1n/ZuBIOaZeR5NMKxhRu639 3mgg== 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 o2-v6si2470869plk.457.2018.03.14.13.43.55; Wed, 14 Mar 2018 13:44:10 -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 S1752338AbeCNUlf (ORCPT + 99 others); Wed, 14 Mar 2018 16:41:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:57254 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752187AbeCNUlc (ORCPT ); Wed, 14 Mar 2018 16:41:32 -0400 Received: from jouet.infradead.org (unknown [179.97.41.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3663E2077A; Wed, 14 Mar 2018 20:41:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3663E2077A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Received: by jouet.infradead.org (Postfix, from userid 1000) id 5FEAB143FAF; Wed, 14 Mar 2018 17:41:29 -0300 (-03) Date: Wed, 14 Mar 2018 17:41:29 -0300 From: Arnaldo Carvalho de Melo To: Sukadev Bhattiprolu Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Ingo Molnar , Namhyung Kim , Jiri Olsa Subject: Re: [GIT PULL] Please pull JSON files for POWR9 PMU events Message-ID: <20180314204129.GH27335@kernel.org> References: <20180313224647.GA22960@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180313224647.GA22960@us.ibm.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Tue, Mar 13, 2018 at 03:46:47PM -0700, Sukadev Bhattiprolu escreveu: > > Hi Arnaldo, > > Please pull an update to the JSON files for POWER9 PMU events. Can you please be a bit more verbose in the next pull requets, something like describing what is the nature of this specific pull request, say it is to better support some specific measurements, etc, so that people don't have to go and peruse the patches looking for what has changed. If you could even show it being used and drawind some interesting conclusion, even better. Or point to documentation describing it being used, a blog post, whatever that clarifies these updates and encourages potential users to try the perf tools with those events. - Arnaldo > The following changes since commit 90d2614c4d10c2f9d0ada9a3b01e5f43ca8d1ae3: > > perf test: Fix exit code for record+probe_libc_inet_pton.sh (2018-03-13 15:14:43 -0300) > > are available in the git repository at: > > https://github.com/sukadev/linux/ p9-json-v5 > > for you to fetch changes up to 99c9dff949f2502964005f9afa8d60c89b446f2c: > > perf vendor events: Update POWER9 events (2018-03-13 16:48:12 -0500) > > ---------------------------------------------------------------- > Sukadev Bhattiprolu (1): > perf vendor events: Update POWER9 events > > .../perf/pmu-events/arch/powerpc/power9/cache.json | 25 --- > .../pmu-events/arch/powerpc/power9/frontend.json | 10 - > .../pmu-events/arch/powerpc/power9/marked.json | 5 - > .../pmu-events/arch/powerpc/power9/memory.json | 5 - > .../perf/pmu-events/arch/powerpc/power9/other.json | 241 ++++++++++++++------- > .../pmu-events/arch/powerpc/power9/pipeline.json | 50 ++--- > tools/perf/pmu-events/arch/powerpc/power9/pmc.json | 5 - > .../arch/powerpc/power9/translation.json | 10 +- > 8 files changed, 178 insertions(+), 173 deletions(-)