From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org, paulmck@us.ibm.com
Cc: arjan@infradead.org, pavel@ucw.cz, akpm@osdl.org,
dipankar@in.ibm.com, vatsa@in.ibm.com, rusty@au1.ibm.com,
mingo@elte.hu, manfred@colorfullife.com, gregkh@kroah.com
Subject: Re: [PATCH] RCU torture-testing kernel module
Date: Sun, 23 Oct 2005 09:22:18 +0200 [thread overview]
Message-ID: <200510230922.26550.ioe-lkml@rameria.de> (raw)
In-Reply-To: <20051022231214.GA5847@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
Hi Paul,
On Sunday 23 October 2005 01:12, Paul E. McKenney wrote:
> --- linux-2.6.14-rc2/kernel/Kconfig.preempt 2005-08-28 16:41:01.000000000 -0700
> +++ linux-2.6.14-rc2-RCUtorturemod/kernel/Kconfig.preempt 2005-10-22 08:24:42.000000000 -0700
> @@ -63,3 +63,15 @@ config PREEMPT_BKL
> Say Y here if you are building a kernel for a desktop system.
> Say N if you are unsure.
>
> +config RCU_TORTURE_TEST
> + tristate "torture tests for RCU"
> + default n
Please put this into lib/Kconfig.debug and make it dependent on
DEBUG_KERNEL there, which illustrates its actual purpose much better.
Regards
Ingo Oeser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-23 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 23:12 Paul E. McKenney
2005-10-23 7:22 ` Ingo Oeser [this message]
2005-10-23 14:36 ` Paul E. McKenney
2005-10-23 18:55 ` Ingo Oeser
2005-10-23 19:05 ` Andrew Morton
2005-10-24 0:47 ` Paul E. McKenney
2005-10-24 14:59 ` Ingo Oeser
2005-10-24 16:24 ` Badari Pulavarty
2005-10-24 17:59 ` Kyle Moffett
2005-10-24 18:10 ` Badari Pulavarty
2005-10-24 22:29 ` Kyle Moffett
2005-10-24 23:03 ` Paul E. McKenney
2005-10-24 22:54 ` Paul E. McKenney
2005-10-24 23:09 ` Badari Pulavarty
2005-10-23 19:47 ` Greg KH
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=200510230922.26550.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dipankar@in.ibm.com \
--cc=gregkh@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=pavel@ucw.cz \
--cc=rusty@au1.ibm.com \
--cc=vatsa@in.ibm.com \
/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
all inboxes | Powered by JetHome®