Hi Ashok, Thanks, I'll find somewhere to put this. For everyone else, does it make more sense to put all these tests together into a single suite, or to group them together for what they're testing, i.e. memory tests, cpu tests? Mark On Wed, Dec 08, 2004 at 10:43:26AM -0800, Ashok Raj wrote: > On Wed, Dec 08, 2004 at 11:52:53AM -0600, Joel Schopp wrote: > > This is the test i use for regression testing on IPF. I havent read > all the test senarious, but its important to test if irq will migrate to this new > cpu, and also when the cpu will go away, we can handle without loss of work > transparently. > > Attached is a simple shell script. The only one that is hard coded is the irq numbers > which can be obtained from /proc/interrupts as well. > > SInce IPF we dont support boot cpu removal, (due to restriction with CPEI, btw > this will go away when platforms support ACPI 3.0) the script doesnt really try > removing cpu0. > > The script is a little flaky, i.e we dont check if current state is offline/online > etc, it might be better to build those in if we need some robustness. > > In addition, i leave some time after an online, before i offline (in parallel > there are ltptest and some make -j running for load) so we let some work be handled > on this cpu as well before offlining. > > > hope this helps. > > Cheers, > ashok
