From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Tilman Schmidt <tilman@imap.cc>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)
Date: Mon, 21 Jun 2010 09:46:14 -0700 [thread overview]
Message-ID: <20100621164614.GD2354@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100621101425.GA20317@bombadil.infradead.org>
On Mon, Jun 21, 2010 at 06:14:26AM -0400, Kyle McMartin wrote:
> On Sun, Jun 20, 2010 at 08:16:05AM -0700, Paul E. McKenney wrote:
> > My kneejerk reaction is that PROVE_RCU is a developer tool, so I am
> > OK with it not being set by default in Rawhide. Or have you seen good
> > value from (say) PROVE_LOCKING in Rawhide?
>
> Hi Paul,
>
> I'm fine with this, we try to enable debug options in rawhide in order
> to get the most out of bug reports/dmesgs that we can. We've definitely
> spotted a lot of lockdep reports by having it enabled for general
> desktop use cases (but as debugging has become more intensive, the perf
> loss from having it enabled is more costly.)
>
> I suspect we'll be OK with PROVE_RCU off though.
Sounds good -- but please feel free to bug me about this again if it turns
out that you are seeing too many testing escapes from Rawhide into RHEL.
Until then, my thought is that PROVE_RCU testing should primarily be done
by developers on development trees.
Thanx, Paul
prev parent reply other threads:[~2010-06-21 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 21:04 CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map) Tilman Schmidt
2010-03-29 15:09 ` Paul E. McKenney
2010-03-29 17:53 ` Tilman Schmidt
2010-03-29 18:40 ` Paul E. McKenney
2010-06-17 10:37 ` Kyle McMartin
2010-06-20 15:16 ` Paul E. McKenney
2010-06-21 10:14 ` Kyle McMartin
2010-06-21 16:46 ` Paul E. McKenney [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=20100621164614.GD2354@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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