STUFF TO DO
--------------------------------------
* "hlt" a disabled CPU?
	or maybe do something useful on it?
	use smp_stop_cpu_interrupt ?
* test suite:
	finish
	automate
	make mksafe/mkunsafe generic
* lmbench tests:
	non-preemptive ?
	isolated
	normal
	no-pset support compiled!
* make it work on 2.3.x
* make it more scheduler generic?
* make a redhat/ dir with a .spec file
* FIXMEs and FIXME questions...
* use/modify cpu_online_map?
* Fix NONPREEMPTIVE semantics:
    - Should non-preemptive REALLY be nonpreemptive?: ie sched runs prev ?
    - Does non-preemptive presume MUSTRUN correctly?  should it?
    - Cleanup MP_NONPREEMPTIVE when proc exit()s..
* Update/create man pages for linux
* validate all is OK on UP system - cut any fat
* RPM the pset-utils package
* What if we empower if not restricted, unisolate if not isolated...
	silently fail - only mark enabled if it WAS isolated..?
		this is how it is now - clean it up...
	should this fail instead?
* What if isolate is already isolated
	return -EALREADY?
	return -EBUSY? <-- currently...is EALREADY more correct?
* Can we get rid of pda_stat and call it cpu_stat, and stay compatible
    - I hate 'stat'  maybe cpu_state - its not stats, but states we track..
* New ideas 
    - reserve a CPU for a UID?
    - MP_FINDPSETLIKE <- find a pset that matches the cpumask specified
      for stuff like 'runon 1,3 cmd'
    - should users be able to create/delete psets?  We'd have to destroy them 
      eventually(?) (at logout?) - like semaphores
* /etc/psettab file for name<->pset translation
* user tools
	finish pset user pgm 
	make "runon" accept multiple CPUs (create a pset on the fly?)
	tools from other UNIXes
	new ones?
* library compatible with Sun, DEC, AIX, ... too
	What other functionality is needed for libsysmp?
* Use write_lock or write_lock_irq or write_lock_irqsave ?
	which ones and where?
* make ps and top show CPU and pset info
* Update/finish Configure.help
	kernel size increase
	URL for tools
* Finish Documentation/pset.txt