Re: [PATCH -tip-rcu] Make rcutorture more vicious: make quiescent rcutorture less power-hungry

On Sun, Jun 22, 2008 at 10:06 PM, Paul E. McKenney<paulmck@linux.vnet.ibm.com> wrote:> This patch makes the non-module rcutorture a bit more friendly to> the power-conservation code. This is a rather simple-minded approach.> More sophisticated approaches would get rid of the rcutorture tasks> while rcutorture execution was suppressed, but attempts thus far to> do this have not gone well -- calling rcu_torture_init() from a /proc> callout results in oopses.

Hi Paul,

I applied your three patches

[PATCH] Make rcutorture more vicious: add stutter feature[PATCH] Make rcutorture more vicious: reinstate boot-time testing[PATCH -tip-rcu] Make rcutorture more vicious: make quiescentrcutorture less power-hungry

to v2.6.26-rc7 and gave it a quick testing in qemu. But it seems tohang during gdb self-tests at boot:

As a convenience feature, it would be nice to have a boot optioncontrolling the run-at-boot as well, simply because it saves arecompile for me :-) Actually, for some reason, the test still startsat boot even when CONFIG_RCU_TORTURE_TEST_RUNNABLE=n. Is a hunkmissing from patch #2?

Vegard

-- "The animistic metaphor of the bug that maliciously sneaked in whilethe programmer was not looking is intellectually dishonest as itdisguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036