LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH REPOST for 2.6.25] Use an own random generator for pageattr-test.c
Date: Tue, 11 Mar 2008 23:11:44 +0100	[thread overview]
Message-ID: <20080311221144.GC428@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0803112248550.3781@apollo.tec.linutronix.de>

> The only bug that code ever caught aside of tons of false positives

It caught bugs when I originally worked on cpa. However that 
had still the revert code and admittedly several were in 
that area (I'm still suspecting at some point you'll have
to readd that -- perhaps it'll be more useful for you then)

However I had originally a longer runtime length too, but later
decreased it when I sent out the patch (since i didn't want 
to submit another "rcu torture" which runs for hours...) 
Perhaps the result was a little too short too, that's possible.

> Finding a bug, when it was exposed by a static pattern, is trivial,
> but the challenge is to make such tests useful enough with random
> patterns. And there are ways to do that, e.g. by making the debug
> output informative enough to provide information about the problem in
> detail instead of printing some useless info "a != b".

Ok I admit I don't know how to do that effectively for cpa, but perhaps
you do.

-Andi


      reply	other threads:[~2008-03-11 22:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  1:30 Andi Kleen
2008-03-11  2:39 ` Andrew Morton
2008-03-11  8:25 ` Thomas Gleixner
2008-03-11 10:45   ` Andi Kleen
2008-03-11 11:41     ` Thomas Gleixner
2008-03-11 11:48       ` Andi Kleen
2008-03-11 21:08         ` Thomas Gleixner
2008-03-11 21:49           ` Andi Kleen
2008-03-11 21:59             ` Thomas Gleixner
2008-03-11 22:11               ` Andi Kleen [this message]

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=20080311221144.GC428@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --subject='Re: [PATCH REPOST for 2.6.25] Use an own random generator for pageattr-test.c' \
    /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

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).