From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
weilin.wang@intel.com
Subject: Re: [PATCH v1 1/1] perf test: make metric validation test return early when there is no metric supported on the test system
Date: Tue, 30 Jul 2024 16:14:28 -0300 [thread overview]
Message-ID: <Zqk7lIhoKHh0ZYGm@x1> (raw)
In-Reply-To: <CAP-5=fWu09Oy0bYjqW921NXgh33GOeCZ-J_tQ9PqPHT7XpY4DA@mail.gmail.com>
On Tue, Jul 30, 2024 at 11:44:32AM -0700, Ian Rogers wrote:
> On Mon, Jul 15, 2024 at 3:25 PM Ian Rogers <irogers@google.com> wrote:
> >
> > On Fri, May 24, 2024 at 6:26 PM Ian Rogers <irogers@google.com> wrote:
> > >
> > > On Wed, May 22, 2024 at 1:43 PM <weilin.wang@intel.com> wrote:
> > > >
> > > > From: Weilin Wang <weilin.wang@intel.com>
> > > >
> > > > Add a check to return the metric validation test early when perf list metric
> > > > does not output any metric. This would happen when NO_JEVENTS=1 is set or in a
> > > > system that there is no metric supported.
> > > >
> > > >
> > > > Signed-off-by: Weilin Wang <weilin.wang@intel.com>
> > >
> > > Tested-by: Ian Rogers <irogers@google.com>
> >
> > Ping.
>
> Ping.
Thanks, applied to tmp.perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2024-07-30 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 20:42 [PATCH v1 1/1] perf test: make metric validation test return early when there is no metric supported on the test system weilin.wang
2024-05-25 1:26 ` Ian Rogers
2024-07-15 22:25 ` Ian Rogers
2024-07-30 18:44 ` Ian Rogers
2024-07-30 19:14 ` 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=Zqk7lIhoKHh0ZYGm@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@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=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@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;
as well as URLs for NNTP newsgroup(s).