From: Dave Jones <davej@redhat.com>
To: Mikko Rapeli <mikko.rapeli@iki.fi>
Cc: trinity@vger.kernel.org
Subject: Re: workaround/blacklist/exclude perf?
Date: Tue, 8 Oct 2013 13:31:59 -0400 [thread overview]
Message-ID: <20131008173159.GA20593@redhat.com> (raw)
In-Reply-To: <20131008152209.GZ7782@lakka.kapsi.fi>
On Tue, Oct 08, 2013 at 06:22:09PM +0300, Mikko Rapeli wrote:
> Is there some simple trick to exclude a single test case which produces
> an oops?
>
> I'm hitting one of the perf issues after few minutes but would like to
> continue testing other kernel subsystems.
The perf bugs are nasty. You can try -x perf_event_open, (and also edit
open_perf_fds in perf.c to just return instantly, but in my experience even
with this, somehow we still end up triggering perf stuff. I've no explanation for it.
Dave
next prev parent reply other threads:[~2013-10-08 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 15:22 workaround/blacklist/exclude perf? Mikko Rapeli
2013-10-08 17:31 ` Dave Jones [this message]
2013-10-09 6:58 ` Mikko Rapeli
2013-10-10 21:31 ` Vince Weaver
-- strict thread matches above, loose matches on Subject: below --
2013-10-08 17:25 Toralf Förster
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=20131008173159.GA20593@redhat.com \
--to=davej@redhat.com \
--cc=mikko.rapeli@iki.fi \
--cc=trinity@vger.kernel.org \
/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