linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Kajol Jain <kjain@linux.ibm.com>, Jiri Olsa <jolsa@redhat.com>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	maddy@linux.ibm.com
Subject: Re: [PATCH] perf test: Fix metric parsing test
Date: Mon, 30 Nov 2020 09:10:56 -0300	[thread overview]
Message-ID: <20201130121056.GB20959@kernel.org> (raw)
In-Reply-To: <CAP-5=fX76BQMaOnKTCgBD9MMwx_Q=tShDFBYZxzJOreOhXV=Mw@mail.gmail.com>

Em Thu, Nov 19, 2020 at 08:48:57AM -0800, Ian Rogers escreveu:
> On Thu, Nov 19, 2020 at 7:25 AM Kajol Jain <kjain@linux.ibm.com> wrote:
> > Result in power9 platform after this patch:

> > [command]# ./perf test 10
> > 10: PMU events                                                      :
> > 10.1: PMU event table sanity                                        : Ok
> > 10.2: PMU event map aliases                                         : Ok
> > 10.3: Parsing of PMU event table metrics                            : Skip
> > (some metrics failed)
> > 10.4: Parsing of PMU event table metrics with fake PMUs             : Ok

> > Fixes: e1c92a7fbbc5 ("perf tests: Add another metric parsing test")
> > Signed-off-by: Kajol Jain <kjain@linux.ibm.com>

> Acked-by: Ian Rogers <irogers@google.com>



Thanks, applied.

- Arnaldo


      parent reply	other threads:[~2020-11-30 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 15:24 [PATCH] perf test: Fix metric parsing test Kajol Jain
2020-11-19 19:32 ` Jiri Olsa
     [not found] ` <CAP-5=fX76BQMaOnKTCgBD9MMwx_Q=tShDFBYZxzJOreOhXV=Mw@mail.gmail.com>
2020-11-30 12:10   ` 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=20201130121056.GB20959@kernel.org \
    --to=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).