Lines Matching +refs:is +refs:scheduled +refs:pipeline

11 The CONFIG_RCU_TORTURE_TEST config option is available for all RCU
15 command (perhaps grepping for "torture").  The test is started
16 when the module is loaded, and stops when the module is unloaded.
24 The statistics output is as follows::
52 	containing structures to be placed into the "rtc" area is empty.
53 	This condition is important, since it can fool you into thinking
54 	that RCU is working when it is not.  :-/
59 	failed due to the list being empty.  It is not unusual for this
60 	to be non-zero, but it is bad for it to be a large fraction of
70 	family of functions is not working correctly.
92 	If any entries past the first two are non-zero, RCU is broken.
94 	you notice.  The age of a newly allocated structure is zero,
95 	it becomes one when removed from reader visibility, and is
96 	incremented once per grace period subsequently -- and is freed
106 	entries is again two.  The reason for this separate view is that
107 	it is sometimes easier to get the third entry to show up in the
111 	that have reached a given point in the pipeline.  The first element
116 	as it is only incremented if a torture structure's counter
129 "old" and "current" values to the underlying array, and is useful for
135 It is sometimes desirable to torture RCU on a specific kernel build,
160 When using rcutorture to test changes to RCU itself, it is often
167 script is available for mainline testing for x86, arm64, and
181 but rather tell you how the tests would be scheduled into batches.  This
208 Sometimes additional debugging is useful, and in such cases the --kconfig
225 Sometimes all that is needed is a full set of kernel builds.  This is
242 is listed at the end of the kvm.sh output, which you really should redirect
243 to a file.  The build products and console output of each run is kept in
251 However, it is often more convenient to access the files directly.
260 The most frequently used file in the top-level directory is testid.txt.
315 This is why kvm-again.sh exists.
338 Although kvm.sh is quite useful, its testing is confined to a single
339 system.  It is not all that hard to use your favorite framework to cause
345 And this is why the kvm-remote.sh script exists.
364 The kvm.sh ``--dryrun scenarios`` argument is useful for working out