mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-kernel <Linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	"Liang, Kan" <kan.liang@intel.com>,
	yao.jin@intel.com, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH] perf vendor events: Update Skylake client events to v50
Date: Fri, 13 Nov 2020 16:12:37 +0800	[thread overview]
Message-ID: <38be0597-7f93-0aa1-b4c5-3c7f23b74f13@linux.intel.com> (raw)
In-Reply-To: <CAM9d7chhrYh1hmHkw8NKkwEHDoU0q2ArpOj3NGm0_RiQ7eSuxQ@mail.gmail.com>

Hi Andi, Ian,

On 11/6/2020 12:21 PM, Namhyung Kim wrote:
> On Fri, Nov 6, 2020 at 12:12 PM Jin, Yao <yao.jin@linux.intel.com> wrote:
>>
>> Hi Namhyung,
>>
>> On 11/6/2020 11:00 AM, Namhyung Kim wrote:
>>> Hi,
>>>
>>> On Wed, Nov 04, 2020 at 09:51:02AM +0800, Jin Yao wrote:
>>>> - Update Skylake events to v50.
>>>> - Update Skylake JSON metrics from TMAM 4.0.
>>>> - Fix the issue in DRAM_Parallel_Reads
>>>> - Fix the perf test warning
>>>>
>>>> Before:
>>>>
>>>> root@kbl-ppc:~# perf stat -M DRAM_Parallel_Reads -- sleep 1
>>>> event syntax error: '{arb/event=0x80,umask=0x2/,arb/event=0x80,umask=0x2,thresh=1/}:W'
>>>>                        \___ unknown term 'thresh' for pmu 'uncore_arb'
>>>>
>>>> valid terms: event,edge,inv,umask,cmask,config,config1,config2,name,period,percore
>>>>
>>>> Initial error:
>>>> event syntax error: '..umask=0x2/,arb/event=0x80,umask=0x2,thresh=1/}:W'
>>>>                                     \___ Cannot find PMU `arb'. Missing kernel support?
>>>>
>>>> root@kbl-ppc:~# perf test metrics
>>>> 10: PMU events                                 :
>>>> 10.3: Parsing of PMU event table metrics               : Skip (some metrics failed)
>>>> 10.4: Parsing of PMU event table metrics with fake PMUs: Ok
>>>> 67: Parse and process metrics                  : Ok
>>>>
>>>> After:
>>>>
>>>> root@kbl-ppc:~# perf stat -M MEM_Parallel_Reads -- sleep 1
>>>>
>>>>    Performance counter stats for 'system wide':
>>>>
>>>>            4,951,646      arb/event=0x80,umask=0x2/ #    26.30 MEM_Parallel_Reads       (50.04%)
>>>>              188,251      arb/event=0x80,umask=0x2,cmask=1/                                     (49.96%)
>>>>
>>>>          1.000867010 seconds time elapsed
>>>>
>>>> root@kbl-ppc:~# perf test metrics
>>>> 10: PMU events                                 :
>>>> 10.3: Parsing of PMU event table metrics               : Ok
>>>> 10.4: Parsing of PMU event table metrics with fake PMUs: Ok
>>>> 67: Parse and process metrics                  : Ok
>>>>
>>>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>>>
>>> It seems not applied to acme/perf/core cleanly.
>>>
>>> Thanks,
>>> Namhyung
>>>
>>
>> It seems the patch mail is truncated. :(
>>
>> I attach the patch file in the mail. Sorry for inconvenience.
> 
> I've checked it fixed the perf test on my laptop (skylake).
> 
> Tested-by: Namhyung Kim <namhyung@kernel.org>
> 
> Thanks,
> Namhyung
> 

Can I get ACK for this patch?

It's mainly for fixing the perf-test issue and MEM_Parallel_Reads issue.

Thanks
Jin Yao

  reply	other threads:[~2020-11-13  8:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  1:51 Jin Yao
2020-11-06  3:00 ` Namhyung Kim
2020-11-06  3:11   ` Jin, Yao
2020-11-06  4:21     ` Namhyung Kim
2020-11-13  8:12       ` Jin, Yao [this message]
2020-11-15 13:35         ` Andi Kleen
     [not found]           ` <CAP-5=fW-9oj4PK=hBmvrCqfzLnoqTe502FRb74Jwqpo+3KoJKw@mail.gmail.com>
2020-11-16  8:07             ` Jin, Yao
2020-11-16 14:53             ` Andi Kleen
2020-11-16 17:05       ` Arnaldo Carvalho de Melo
     [not found]         ` <CAP-5=fXJCqB6sN+f-eRSwc+Za3Yri+QWMpg_G7xfz=i-cTBH3A@mail.gmail.com>
2020-11-16 19:24           ` Arnaldo Carvalho de Melo
2020-11-16 21:24             ` Andi Kleen

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=38be0597-7f93-0aa1-b4c5-3c7f23b74f13@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.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

Powered by JetHome