All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>,
	"Namhyung Kim" <namhyung@kernel.org>,
	Jin Yao <yao.jin@linux.intel.com>,
	"Paul A . Clarke" <pc@us.ibm.com>,
	<linux-perf-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <eranian@google.com>
Subject: Re: [PATCH v3 1/2] perf test: Workload test of metric and metricgroups
Date: Wed, 12 Jan 2022 17:32:56 +0000	[thread overview]
Message-ID: <e7b20497-e2bb-0c63-3cea-b6f541e2361f@huawei.com> (raw)
In-Reply-To: <BD3A5CA5-B566-4FD9-9409-0329CC322060@gmail.com>

On 12/01/2022 13:34, Arnaldo Carvalho de Melo wrote:
>>>> v3. Fix test condition (thanks to Paul A. Clarke<pc@us.ibm.com>). Add a
>>>>       fallback case of a larger workload so that we don't ignore "<not
>>>>       counted>".
>>>> v2. Switched the workload to something faster.
>> Hi Ian,
>>
>> I just noticed that this test fails on my broadwell machine.
>>
>> I am using acme perf/core @ 09dd3c22daaf
> Hi,
> 
> Can you try with tmp.perf/perf_cpu instead?
> 
> There's a patch there that maybe fixes this.

Yeah, that (metricgroups) test passes on that branch. I assume it's the 
test script -a change...

Cheers,
john

  reply	other threads:[~2022-01-12 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 18:42 [PATCH v3 1/2] perf test: Workload test of metric and metricgroups Ian Rogers
2021-09-17 18:42 ` [PATCH v3 2/2] perf test: Workload test of all PMUs Ian Rogers
2021-09-24 19:09 ` [PATCH v3 1/2] perf test: Workload test of metric and metricgroups Arnaldo Carvalho de Melo
2021-09-24 19:39   ` John Garry
2021-09-28 18:55     ` Arnaldo Carvalho de Melo
2022-01-12 12:24   ` John Garry
2022-01-12 13:34     ` Arnaldo Carvalho de Melo
2022-01-12 17:32       ` John Garry [this message]
2022-01-12 17:59         ` Arnaldo Carvalho de Melo
2022-01-12 18:00           ` John Garry

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=e7b20497-e2bb-0c63-3cea-b6f541e2361f@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@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.