Decide what 'available' processors means on native threads

Typically, a native threading JVM would answer this by telling you how many CPUs (real or virtual if in an LPAR) you had to run on. Suggest we do the same.

Moving all unscheduled issues to 3.1. Please close or retarget to a different fix target as appropriate.

Defer to 3.1.1

This issue affects the Dacapo 9.12 benchmarks. The Dacapo harness uses Runtime.availableProcessors() to scale workloads. In Jikes RVM 3.1.0, the value defaults to 1 regardless of the actual number of processors in the system. The value is pulled from the RVMThread.processors field, which specifies the number of collector threads in the system and defaults to 1.

bulk defer open issues to 3.1.2

bulk defer to 3.1.4