From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: zhengjun.xing@linux.intel.com, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@intel.com, jolsa@kernel.org,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, ak@linux.intel.com,
kan.liang@linux.intel.com
Subject: Re: [PATCH] perf test: Fix test case 87 ("perf record tests") for hybrid systems
Date: Thu, 29 Sep 2022 09:53:37 -0300 [thread overview]
Message-ID: <YzWVUUHSsckvR5Xn@kernel.org> (raw)
In-Reply-To: <CAP-5=fVgsMzx6F=rgy9kyfWS=Gj3hvtLTJmTzf6+O954x4oY_g@mail.gmail.com>
Em Wed, Sep 28, 2022 at 07:11:15PM -0700, Ian Rogers escreveu:
> On Wed, Sep 28, 2022 at 7:28 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Em Tue, Sep 27, 2022 at 01:15:13PM +0800, zhengjun.xing@linux.intel.com escreveu:
> > > From: Zhengjun Xing <zhengjun.xing@linux.intel.com>
> > >
> > > The test case 87 ("perf record tests") failed on hybrid systems,the event
> > > "cpu/br_inst_retired.near_call/p" is only for non-hybrid system. Correct
> > > the test event to support both non-hybrid and hybrid systems.
> > >
> > > Before:
> > > # ./perf test 87
> > > 87: perf record tests : FAILED!
> > >
> > > After:
> > > # ./perf test 87
> > > 87: perf record tests : Ok
> >
> > Looks sane, applied.
> >
> > Ian, consider providing your Acked-by,
> Acked-by: Ian Rogers <irogers@google.com>
Thanks, added.
- Arnaldo
prev parent reply other threads:[~2022-09-29 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 5:15 [PATCH] perf test: Fix test case 87 ("perf record tests") for hybrid systems zhengjun.xing
2022-09-28 14:28 ` Arnaldo Carvalho de Melo
2022-09-29 2:11 ` Ian Rogers
2022-09-29 12:53 ` 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=YzWVUUHSsckvR5Xn@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.