[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1105241616280.24062@cl320.eecs.utk.edu>
Date: Tue, 24 May 2011 16:31:11 -0400 (EDT)
From: Vince Weaver <vweaver1@...s.utk.edu>
To: Ingo Molnar <mingo@...e.hu>
cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, fbuihuu@...il.com, paulus@...ba.org,
acme@...hat.com
Subject: Re: perf: regression with PERF_EVENT_IOC_REFRESH
On Tue, 24 May 2011, Ingo Molnar wrote:
>
> Btw., how did it happen that the PAPI tests did not get run against upstream
> over the course of about half a year, two full stable kernels released:
we run regresion tests nightly. There was a bug in our
"create two events and sample on the second"
test, where it was actualy sampling on the first counter by mistake.
When I fixed the test to do what it claimed to do it found the bug.
PAPI runs on at least 5 different operating systems, 3 different
Linux perf counter implementations, and on kernels dating back to 2.4.
Plus numerous architectures. While we try to test against recent
Linux perf_events, we just don't have the hardware to be comprehensive.
It doesn't help that our test machines are primarily used for GPGPU work
during the day, so we're limited to what kernels we can have installed
due to driver issues.
> suggest moving these usecases into 'perf test' or so - that it gets run every
> day:
you can feel free to install PAPI on your test machines and give it a run
daily too. It's open source
setenv CVSROOT :pserver:anonymous@....eecs.utk.edu:/cvs/homes/papi
cvs login
cvs co all
cd papi
./configure
make
./run_tests
There are often false negatives on the tests that can be a pain
to track down. Welcome to my world. We gladly accept patches.
Vince
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists