Core Devices
Table of Contents
- 1 CPU
- 2 RAM
- 2.1 size
- 3 TOY
- 3.1 container
- 3.2 sync_to_host
- 3.3 Example
- 4 ROM
- 4.1 container
- 4.2 system_name
- 4.3 system_serial_number
- 4.4 dsrdb
- 4.5 version
- 5 Virtual HP Alpha interval timer
- 6 Setting of a particular HP Alpha model
- 6.1 HP AlphaStation 200 - 400
- 6.2 HP AlphaServer 600 - 800
- 6.3 HP AlphaServer 1000
- 6.4 HP AlphaServer 1000A
- 6.5 HP AlphaServer 1200 and AlphaStation 1200
- 6.6 HP AlphaServer 2000
- 6.7 HP AlphaServer 2100
- 6.8 HP AlphaServer 4000
- 6.9 HP AlphaServer 4100
- 6.10 HP AlphaServer/AlphaStation DS10 and HP AlphaServer DS10L
- 6.11 HP AlphaServer DS15 and HP AlphaStation DS15
- 6.12 HP AlphaServer DS20 and HP AlphaStation DS20
- 6.13 HP AlphaServer DS25 and HP AlphaStation DS25
- 6.14 HP AlphaServer ES40 and AlphaStation ES40
- 6.15 HP AlphaServer ES45
- 6.16 HP AlphaServer GS80
- 6.17 HP AlphaServer GS160
- 6.18 HP AlphaServer GS320
- 7 Auto Boot
- 8 Setting System Marketing Model (SMM)
CPU
The CHARON Virtual Machine (VM) CPU can be calibrated with "set ace" directive and the following parameters:
enabled
Parameter | enabled | |
|---|---|---|
Type | Boolean | |
Value | A CHARON-AXP emulated CPU is configured with the "enabled" command enabling the high performance Advanced CPU Emulation mode ("ACE"). The ACE option optimizes the HP Alpha instruction interpretation and significantly improves performance. It also requires approximately twice the amount of host memory allocated by CHARON instance itself to store the optimized code (Note that 2Gb of host memory + the amount of HP Alpha memory emulated per each CHARON instance is required). ACE optimization is performed dynamically during execution. It does not need to write optimized code back to disk, ACE provides its full capability instantly. The optimization does not compromise the HP Alpha instruction decoding; CHARON-AXP remains fully HP Alpha hardware compatible and completely transparent to the HP Alpha operating systems and applications. This configuration setting enables the ACE mode if the CHARON-AXP license permits it. If this configuration setting is omitted from the CHARON VM configuration file and the license permits it, "true" is the default, otherwise "false" is the default. Example:
" The ACE mode is disabled when the host system does not meet the minimum physical requirements for this operation. If the emulator appears not to run at its normal performance, check the log file for a change in the ACE mode and verify that sufficient host resources, especially memory, are available. |
cpu_architecture
Parameter | cpu_architecture | |
|---|---|---|
Type | Text String | |
Value | Specifies the architecture of the virtual Alpha CPU. Can be one of the following: EV4, EV45, EV5, EV56, EV6, EV67, EV68 Example:
Refer to Setting of a particular HP Alpha model to find an appropriate value of the HP Alpha architecture per each HP Alpha model supported by CHARON-AXP. |
cache_size
Parameter | cache_size | |
|---|---|---|
Type | Value | |
Value | This parameter may affect Charon performance. Do not change this parameter until advised by Stromasys "cache_size" defines the amount of memory in megabytes allocated to the ACE cache. Default value is 1GB (1024 MB). Example:
This parameter may be changed for performance optimization in case of some guest OS specific tasks (see the section below). |
num_translators
Parameter | num_translators | |
|---|---|---|
Type | Value | |
Value | This parameter may affect Charon performance. Do not change this parameter until advised by Stromasys "num_translators" defines the number of ACE translators. Default value in most situations is number of I/O CPUs dedicated to CHARON (defined by "n_of_io_cpus" parameter) minus 1, but in some specific situations it may be set to some other value for better performance. Example:
|
host_options
Parameter | host_options | |
|---|---|---|
Type | Text String | |
Value | This parameter may affect Charon performance. Do not change this parameter until advised by Stromasys "host_options" defines options of ACE (DIT) translator and code-generator. Those options affect Charon performance. Default settings are set to optimize performance for most geust OS (VMS and Tru64) usage profiles. However there are some profiles (for example OpenVMS compilation tasks) where the default settings do not provide optimal perfromance. The following switches are available to user: 1. --fixed-variant=[X] The value X can be one of three options: [-1, 0, 1]. This value defines the desired translation variant. Set -1 for dynamic (default) or 0 or 1 for the fixed number implemented by the translator. 2. --x64-optimize or --x64-nooptimize This switch enables translation optimizations (the default is to optimize). Default parameters have been changed in Charon version 4.9 compared to previous versions (4.8 and below). If Charon system demonstrates lower performance after upgrade to version 4.9, please test the system with host_options switched to default 4.8 settings:
Note that in this case the parameter "num_translators" must be set to the number of I/O CPUs dedicated to CHARON (see the "n_of_io_cpus" parameter). Also note that changing parameter "cache_size" can be an alternative solution too (see the section below). |