From: Jiri Olsa <jolsa@redhat.com>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-perf-users@vger.kernel.org,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] RFC perf test 14 add platform dependency
Date: Tue, 20 Jun 2017 11:24:31 +0200 [thread overview]
Message-ID: <20170620092431.GA2380@krava> (raw)
In-Reply-To: <4349df01-bc7d-32bc-aa31-04c25ab970c1@linux.vnet.ibm.com>
On Tue, Jun 20, 2017 at 10:12:14AM +0200, Thomas-Mich Richter wrote:
> On 06/20/2017 03:40 AM, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jun 19, 2017 at 10:59:44PM +0200, Jiri Olsa escreveu:
> >> On Tue, Jun 13, 2017 at 11:09:37AM +0200, Thomas Richter wrote:
> >>> This is a proposal to add platform dependency into the
> >>> test case 14 (perf_event_attr). It is based on a suggestion from
> >>> Jiri Olsa.
> >>> Add a new optional attribute named 'machine' in the [config] section
> >>> of the test case file. It is a comma separated list of architecture
> >>> names this test can be executed on. For example:
> >>>
> >>> machine = x86_64,alpha,ppc
> >>
> >> 'arch' sounds better to me, but machine is ok I guess
> >
> > Agreed, for consistency with other places, like in struct machine, that
> > represents virtual and host 'machines' that have an 'arch', etc.
> >
> > So better to rename "machine" above to "arch".
> >
>
> Ok lets rename it to arch.
>
> >>> If this attribute is missing the test is executed on any platform.
> >>> This does not break the current setup.
> >>> The values listed for this attribute should be identical to
> >>> uname -m output.
> >>> If the list starts with an exclamation mark (!) the comparison is
> >>> inverted, for example for
> >>>
> >>> machine = !s390x,ppc
> >>>
> >>> the test is not executed on s390x or ppc platforms.
> >>> The exclamation mark must be at the beginnning of the list.
> >>
> >> could that be per arch? this made me think that it's not s390 and it IS for ppc
> >
> > yeah, having the ! affect just the arch right after it looks more
> > flexible and clear.
> >
>
> Does this really have any benefit? Assume
> arch = !s390x,ppc
>
> I will scan the list from left to right and the first match wins.
> Checking the first word in the list determines
> this test is executed on anything but s390x. So the 2nd word in the
> list (ppc) is useless. Specifying more architectures makes only sense
> when you negate them such as
> arch = !s390x,!ppc
ok, makes sense
thanks,
jirka
next prev parent reply other threads:[~2017-06-20 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 9:09 [PATCH v2] RFC perf test 14 add platform dependency Thomas Richter
2017-06-16 16:08 ` Arnaldo Carvalho de Melo
2017-06-18 22:51 ` Jiri Olsa
2017-06-19 20:59 ` Jiri Olsa
2017-06-20 1:40 ` Arnaldo Carvalho de Melo
2017-06-20 8:12 ` Thomas-Mich Richter
2017-06-20 9:24 ` Jiri Olsa [this message]
2017-06-20 14:06 ` Thomas-Mich Richter
2017-06-20 14:48 ` Arnaldo Carvalho de Melo
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=20170620092431.GA2380@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=tmricht@linux.vnet.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).