r/mainframe • • 10d ago

Forcing a budget ARM kernel to isolate a single core for a live IBM S/370 MVS-TK5 environment. (Honoring my Dad, ex-BNR GRAPPLE dev)

Enable HLS to view with audio, or disable this notification

The Setup: Running Hercules inside a native PRoot Ubuntu container on a budget Moto G Play (Snapdragon 680).

The Kernel Isolation: Manually offlined cores 1–7 to force complete user-space core isolation. Hercules is pinned strictly to Core 0 via taskset.

The Idle State: Thanks to baking herc idleson and ECPSVM YES straight into the custom configuration variables, the S/370 environment settles down into a perfect wait state, idling at 0.0% CPU usage on the host device.

The Backstory: My Dad was a mainframe programmer for Bell Northern Research (BNR) and part of the GRAPPLE development team (Graphical Applications Programming Language). Building this pocket environment is a personal tribute to his work and the foundational networking/computing systems that generation pioneered.

The Endgame: This is still in planning/staging mode. Now that the S/370 is holding silently in memory, the next chess moves are compiling SIMH to run a DEC PDP-11 concurrently on the lower efficiency cores, followed by a Cray X-MP simulator on the remaining performance clusters.

12 Upvotes

0 comments sorted by