public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Andi Kleen <andi@firstfloor.org>, Vince Weaver <vince@deater.net>,
	Matt Fleming <matt.fleming@intel.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH] perf tests: Add Intel CQM and arch tests
Date: Wed, 22 Jul 2015 10:50:58 -0300	[thread overview]
Message-ID: <20150722135058.GB2326@redhat.com> (raw)
In-Reply-To: <20150722132444.GC28330@krava.brq.redhat.com>

Em Wed, Jul 22, 2015 at 03:24:44PM +0200, Jiri Olsa escreveu:
> On Wed, Jul 22, 2015 at 11:38:59AM +0100, Matt Fleming wrote:
> > This patch is marked as RFC because I'd really like to solicit opinions
> > on this approach and hear feedback on whether this is the correct way to
> > structure these arch tests. I realise that we've already got tests for
> > the TSC, etc that are x86-specific but I didn't want to change the order
> > of the tests (say, by moving test__perf_time_to_tsc() into ARCH_TESTS)
> > in case that broke some kind of ABI.
 
> I wouldn't consider the order of tests being ABI,
> let's break it and watch ;-)

yeah
 
> SNIP
 
> > diff --git a/tools/perf/arch/x86/include/arch-tests.h b/tools/perf/arch/x86/include/arch-tests.h
> > +#define ARCH_TESTS						\
> > +	{							\
> > +		.desc = "Test intel cqm nmi context read",	\
> > +		.func = test__intel_cqm_count_nmi_context,	\
> > +	},
> > +
> 
> hum, I dont like much this being stuffed in macro,
> but dont have any technical reason against ;-)
> 
> maybe we could add 'struct test arch_tests[]' array, that'd be
> initialized by each arch and executed in addition to the current
> 'struct test tests[]'

Agreed, that would be cleaner, and we need something like that anyway,
i.e. some way to group tests that run only if certain requirements are
met, i.e. tests that require root permission, arch specific ones, etc.

- Arnaldo

  reply	other threads:[~2015-07-22 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 10:38 [RFC][PATCH] perf tests: Add Intel CQM and arch tests Matt Fleming
2015-07-22 13:24 ` Jiri Olsa
2015-07-22 13:50   ` Arnaldo Carvalho de Melo [this message]
2015-07-22 22:18   ` 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=20150722135058.GB2326@redhat.com \
    --to=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@redhat.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=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