From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Vince Weaver <vince@deater.net>,
Peter Zijlstra <peterz@infradead.org>,
Kanaka Juvva <kanaka.d.juvva@intel.com>,
Vikas Shivappa <vikas.shivappa@intel.com>,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH 0/3] perf tests: Add arch tests
Date: Tue, 8 Sep 2015 11:24:16 -0300 [thread overview]
Message-ID: <20150908142416.GB2435@redhat.com> (raw)
In-Reply-To: <20150907125818.GA23219@krava.brq.redhat.com>
Em Mon, Sep 07, 2015 at 02:58:18PM +0200, Jiri Olsa escreveu:
> On Sat, Sep 05, 2015 at 08:02:19PM +0100, Matt Fleming wrote:
> > From: Matt Fleming <matt.fleming@intel.com>
> >
> > To encourage developers to contribute arch-specific tests without
> > feeling guilty about messing up the generic perf tests, this patch
> > series introduces "arch tests" and then adds a test for the Intel CQM
> > perf code which was used to trigger a WARN_ON_ONCE(), fixed in commit
> > 2c534c0da0a6 ("perf/x86/intel/cqm: Return cached counter value from
> > IRQ context").
> >
> > The concept of additional lists of tests, like the arch tests, can be
> > taken further in the future, for instance Arnaldo has expressed
> > interest in adding tests that require root permissions, etc.
> >
> > The patch series is based on tip/perf/core.
>
> please base this over Arnaldo's perf/core
Yeah, that is better, sometimes, like now, the difference from
tip/perf/core to acme/perf/core can grow as big as 50, 60 patches :-)
BTW I applied the first patch, with Jiri's ack, its in my perf/core
branch now.
- Arnaldo
next prev parent reply other threads:[~2015-09-08 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 19:02 [PATCH 0/3] perf tests: Add arch tests Matt Fleming
2015-09-05 19:02 ` [PATCH 1/3] perf tests: Introduce iterator function for tests Matt Fleming
2015-09-07 12:36 ` Jiri Olsa
2015-09-15 7:00 ` [tip:perf/core] " tip-bot for Matt Fleming
2015-09-05 19:02 ` [PATCH 2/3] perf tests: Add arch tests Matt Fleming
2015-09-07 12:23 ` Jiri Olsa
2015-09-12 11:00 ` Matt Fleming
2015-09-07 12:28 ` Jiri Olsa
2015-09-12 11:03 ` Matt Fleming
2015-09-07 12:29 ` Jiri Olsa
2015-09-12 11:04 ` Matt Fleming
2015-09-05 19:02 ` [PATCH 3/3] perf tests: Add Intel CQM test Matt Fleming
2015-09-07 12:58 ` [PATCH 0/3] perf tests: Add arch tests Jiri Olsa
2015-09-08 14:24 ` Arnaldo Carvalho de Melo [this message]
2015-09-12 10:46 ` Matt Fleming
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=20150908142416.GB2435@redhat.com \
--to=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=kanaka.d.juvva@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=vikas.shivappa@intel.com \
--cc=vince@deater.net \
/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