public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Mamatha Inamdar <mamatha4@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, ravi.bangoria@linux.ibm.com,
	maddy@linux.vnet.ibm.com, peterz@infradead.org,
	mpe@ellerman.id.au, alexander.shishkin@linux.intel.com,
	mingo@redhat.com, namhyung@kernel.org, jolsa@redhat.com
Subject: Re: [PATCH]perf vendor events:Remove P8 HW events which are not supported
Date: Tue, 24 Sep 2019 16:39:46 -0300	[thread overview]
Message-ID: <20190924193946.GB20773@kernel.org> (raw)
In-Reply-To: <20190909065624.11956.3992.stgit@localhost.localdomain>

Em Mon, Sep 09, 2019 at 12:33:33PM +0530, Mamatha Inamdar escreveu:
> This patch is to remove following hardware events
> from JSON file which are not supported on POWER8.
> 
> pm_l3_p0_grp_pump
> pm_l3_p0_lco_data
> pm_l3_p0_lco_no_data
> pm_l3_p0_lco_rty

Thanks, applied.

- Arnaldo
 
> Fixes: c3b4d5c4afb0 ("perf vendor events: Remove P8 HW events which are not supported")
> Note: Unfortunately power8 event list is not publicly available.
> Signed-off-by: Mamatha Inamdar <mamatha4@linux.vnet.ibm.com>
> Acked-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
> ---
>  .../perf/pmu-events/arch/powerpc/power8/other.json |   24 --------------------
>  1 file changed, 24 deletions(-)
> 
> diff --git a/tools/perf/pmu-events/arch/powerpc/power8/other.json b/tools/perf/pmu-events/arch/powerpc/power8/other.json
> index 9dc2f6b7..b2a3df0 100644
> --- a/tools/perf/pmu-events/arch/powerpc/power8/other.json
> +++ b/tools/perf/pmu-events/arch/powerpc/power8/other.json
> @@ -1776,30 +1776,6 @@
>      "PublicDescription": ""
>    },
>    {,
> -    "EventCode": "0xa29084",
> -    "EventName": "PM_L3_P0_GRP_PUMP",
> -    "BriefDescription": "L3 pf sent with grp scope port 0",
> -    "PublicDescription": ""
> -  },
> -  {,
> -    "EventCode": "0x528084",
> -    "EventName": "PM_L3_P0_LCO_DATA",
> -    "BriefDescription": "lco sent with data port 0",
> -    "PublicDescription": ""
> -  },
> -  {,
> -    "EventCode": "0x518080",
> -    "EventName": "PM_L3_P0_LCO_NO_DATA",
> -    "BriefDescription": "dataless l3 lco sent port 0",
> -    "PublicDescription": ""
> -  },
> -  {,
> -    "EventCode": "0xa4908c",
> -    "EventName": "PM_L3_P0_LCO_RTY",
> -    "BriefDescription": "L3 LCO received retry port 0",
> -    "PublicDescription": ""
> -  },
> -  {,
>      "EventCode": "0x84908d",
>      "EventName": "PM_L3_PF0_ALLOC",
>      "BriefDescription": "lifetime, sample of PF machine 0 valid",

-- 

- Arnaldo

      reply	other threads:[~2019-09-24 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  7:03 [PATCH]perf vendor events:Remove P8 HW events which are not supported Mamatha Inamdar
2019-09-24 19:39 ` Arnaldo Carvalho de Melo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190924193946.GB20773@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mamatha4@linux.vnet.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox