Download VAX MP Technical Overview

Transcript
treats all active streams of execution as having equal priority. Therefore despite the processes have
different priority within guest OS, high-priority process will share host core’s execution resources on an
equal basis with lower priority process and will be effectively slowed down by it.
To avoid such slow-down, it may be desirable to configure virtual VAX multiprocessors to have at most
the same number of VCPUs as the number of physical cores on the host system, rather than the number
of host logical processors created by hyper-threading. For example, for host computers utilizing Intel i7
CPU chip that has 4 cores, each of these cores further hyper-threaded to a total of 8 logical processors,
avoidance of sharing the core via hyper-threading would translate to a configuration maximum of 4 VAX
VCPUs, rather than 8 VAX VCPUs.
Furthermore, host operating system may be smart or not smart enough about allocating VCPU threads
to distinct cores when free cores are available instead of lumping two threads to the same core, while
another core may have no threads assigned to it. Ideally, host OS scheduler should be smart enough
about spreading active threads among the cores, trying to avoid sharing the core by two threads, but
whether specific operating system is performing it is undocumented. It appears Windows 7 does it and
Linux does it too (HT-aware passive and active load balancing).
It can be reasonably expected that mainstream modern OSes will be smart about HT/SMT-aware
scheduling. Nevertheless just in case, VAX MP includes code (currently defunct) to set affinity mask for
VCPU threads to a mask that has only one logical processor per core, thus preventing VCPUs from being
co-scheduled on the same core. This code can be enabled by console command
sim> DEPOSIT VCPU_PER_CORE 1
This setting is accepted only if number of VCPUs does not exceed the number of cores.
This code had not been debugged and made functional yet. It has been observed that enabling it on
Windows causes – for some mysterious as of yet reason – one of VCPU threads to be virtually stalled
and executed at near-zero speed, despite the core and logical CPU assigned for it were not utilized. It
had not been tried on Linux yet.
Essential OpenVMS bugs
The latest released version of OpenVMS for VAX was 7.3 (released in 2001) and is available on OpenVMS
VAX Hobbyist CD. Unfortunately with VAX already well underway departing into sunset at that time, 7.3
was not tested as thoroughly as previous versions. There is a bug in OpenVMS 7.3 relevant for VAX MP.
This OpenVMS 7.3 bugs show up even on a regular, original uniprocessor version of VAX SIMH.
Setting MULTIPROCESSOR to 4 apparently does not cause multiprocessing system image to be properly
loaded, as indicated by SHOW CPU. What’s worse, it causes system crash on DISMOUNT of any disk
volume (other than system volume), often wiping out the home block of that volume for a good
101