5 Mar
2018
5 Mar
'18
5:17 a.m.
Hi Mark,
sim> SHOW VERSION
VAX simulator V3.9-0 [64b data, 64b addresses, Ethernet support]
sim>
Running on NetBSD 7.1.1 Rpi2 or 8.4 on AXP
I'll grab the latest master and check it out. I've been curious to see if the
graphical console fb stuff from 9track.net or the vax-mp made it into the mainline.
Al.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark
Pizzolato
Sent: Monday, 5 March 2018 11:58 AM
To: hecnet at Update.UU.SE
Cc: Mark Pizzolato <Mark at infocomm.com>
Subject: RE: [HECnet] KLH10 not idling host CPU
Hi Alastair,
On Sunday, March 4, 2018 at 3:24 PM, Alastair Boyanich wrote:
I can only speak for the VAX side of things, but ymmv
and possibly similar?
I?ve seen this with VMS on the VAX simulator. I think the idle loop
detection changed a while back (perhaps on KLH10 also?) so it wasn?t
detecting the vms idle loop correctly and thus emulating every cycle,
driving the cpu to 100%.
There was an option I used to feed it in the .ini which was:
SET CPU IDLE=VMS
But this has not made much of a difference for a long while. On-topic,
SET CPU IDLE=NETBSD has worked for me. I am unsure of the reasoning.
Simh Idling for VMS running in simulators has worked for all versions of VMS pretty much
from the beginning of any idle features. If you're seeing less than ideal behavior,
please try the latest code from https://github.com/simh/simh/archive/master.zip
If you still don't get good results, please send the output produced by:
sim> SHOW VERSION
in your simulator and identify what host OS you?re running on.
Thanks.
- Mark
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to
copyright and/or is commercial-in-confidence and is intended only for the use of the above
named addressee. If you are not the intended recipient, you are hereby notified that
dissemination, copying or use of the information is strictly prohibited. If you have
received this e-mail in error, please telephone Fujitsu Australia Limited on 02 9776 4555
or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Limited would not knowingly transmit a virus within an email
communication, it is the receiver?s responsibility to scan all communication and any files
attached for computer viruses and other defects. Fujitsu Australia Limited does not accept
liability for any loss or damage (whether direct, indirect, consequential or economic)
however caused, and whether by negligence or otherwise, which may result directly or
indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu
Australia Limited, please email unsubscribe at au.fujitsu.com.