On Wednesday 13 July 2005 09:30 am, Mary Edie Meredith wrote: > On Wed, 2005-07-13 at 09:13 -0700, Mark Delcambre wrote: > > On Wednesday 13 July 2005 08:47 am, Mary Edie Meredith wrote: > > > On Tue, 2005-07-12 at 16:51 -0700, Bryce Harrington wrote: > > > > Mark Delcambre, a summer student working with us at OSDL, has been > > > > helping code the test cases. > > > > > > > > http://developer.osdl.org/dev/hotplug/tests/ > > > > > > > > With this release we now have three of the six test cases > > > > implemented: > > > > > > > > hotplug02: Tasks wrongly migrated to a cpu while it is going > > > > off-line. hotplug03: Tasks not scheduled on a newly on-lined cpu > > > > hotplug04: Allowing admin error of offlining the last remaining cpu. > > > > > > > > Descriptions of the tests are available here: > > > > > > > > > > > > http://www.developer.osdl.org/maryedie/HOTPLUG/planning/hotplug_cpu_t > > > >est_ plan_status.html > > > > > > Bryce/Mark, > > > > > > To make these test cases easy to implement and use, could you > > > please make sure the scripts have comments that state the goal > > > of the test case, if you haven't already? Sorry, I should have > > > thought of this when we went over the Psuedo code. > > > > > > Did you also create an envelop script for the test cases that > > > allows the inner test to be repeated over a long period of time? > > > Or are you going to do the inner tests first, then move on to > > > the repetitions? > > > > I think that it is the case that we will finish with all 6 test cases > > before writing the envelop script. > > It is setup already to loop, you can export the 'totalloops' variable to > > make each script run x amount of times. > > Each test also has its own variable {testcase#}loops (so for testcase03 > > it would be 'threeloops' That will override the totalloops for that test > > Cool. > I assume you figure out what cpus are live on the system in the script. > For some of the test cases that target just one cpu, how do you pick the > cpu to offline/online? For testcase 2 and 3 it is a command line option it will report back to you with a error and give you the proper use. And yes for test 3 and 4 it turns on all CPUs then--after the test completes error or not--turns off the ones that were off before the test was started. Every test should return the computer to the state it was before the test was run. > > > > > Results on the 4-cpu PPC64 machine: > > > > > > > > # for file in hot*.sh; do echo; ./$file 3; done > > > > > > > > Tue Jul 12 16:32:56 PDT 2005 > > > > Hotplug Test: Test Case 2 > > > > Hotplug02 PASS - turned off CPU 3, process migrated to CPU 0 > > > > Tue Jul 12 16:33:03 PDT 2005 > > > > > > > > Tue Jul 12 16:33:03 PDT 2005 > > > > Hotplug Test: Test Case 3 > > > > Hotplug03 PASS: do_spin_loop found on CPU3 > > > > Tue Jul 12 16:33:08 PDT 2005 > > > > > > > > Tue Jul 12 16:33:08 PDT 2005 > > > > Hotplug Test: Test Case 4 > > > > Hotplug04 PASS: Could not shutdown cpu0 > > > > Tue Jul 12 16:33:18 PDT 2005 > > > > > > > > Bryce
