...
General settings that control the execution of CHARON-AXP belong to an object called the "session". It is a preloaded object; therefore, only "set" commands apply.
Example:
set session <parameter>=<value> |
...
The following table describes all available "session" parameters, their meaning and examples of their usage:
hw_model
| Parameter | hw_model | |
|---|---|---|
| Type | Text string | |
| Value | Virtual HP Alpha system hardware model to be emulated. Use a default configuration template for each particular model as a starting point for a custom configuration. This would ensure that the parameter is set correctly. Example:
Available models are:
|
Refer to configuration_name
| Parameter | configuration_name | ||
|---|---|---|---|
| Type | Text string | ||
| Value | Name of the CHARON-AXP instance (ir must be unique):
The value of this parameter is used as a prefix to the event log file name. (see below). From the example above, the CHARON-AXP log file will have the following name:
xxxxxxxxx is an increasing decimal number starting from 000000000 to separate log files with the same time of creation (in case the log is being written faster than one log file per second).
|
It is strictly recommended to use the "log
| Parameter | log | ||||||
|---|---|---|---|---|---|---|---|
| Type | Text string | ||||||
| Value | The log file or directory name is where the log file for each CHARON-AXP execution session is stored. If an existing directory is specified, CHARON-AXP automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted CHARON-AXP creates a log file for each CHARON-AXP execution session in the directory where the emulator was started. It is possible to overwrite the existing log file or extend it using the "log_method" parameter. See below for details. Examples:
If only a directory name is specified in the "log" parameter and the "configuration_name" parameter of the session is specified, the log file name will have the following format:
If only a directory name is specified in the "log" parameter and the "configuration_name" parameter is omitted, the log file name will have the following format:
xxxxxxxxx is an increasing decimal integer, starting from 000000000 to separate log files with the same time of creation (in case the log is being created faster than one log file per second).
|
| Div | ||
|---|---|---|
| ||
|
log_method
| Parameter | log_method | |||
|---|---|---|---|---|
| Type | Text string | |||
| Value |
Determines if the previous log information is maintained or overwritten.
This parameter is applicable only if the CHARON-AXP log is stored to a file that is specified explicitly with the "log" parameter. Example:
|
...
| Parameter | affinity | |||
|---|---|---|---|---|
| Type | Text string | |||
| Value | Overrides any initial process affinity mask provided by the host operating system. Once specified it binds the running instance of the emulator to particular host CPUs. Used for soft partitioning of the host CPU resources and/or for isolating host CPUs for other applications. By default the CHARON-AXP emulator instance allocates as many host CPUs as possible. The “affinity” parameter overrides that and allows explicit specification on which host CPU the instance must run on.
Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:
|
| Div | ||
|---|---|---|
| ||
|
| Anchor | ||||
|---|---|---|---|---|
|
...
| Parameter | n_of_cpus | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Numeric | |||||||||||||||||||||||||||||||||||||||
| Value | Limits the number of emulated CPUs. Example:
The maximum number of CPUs enabled by CHARON-AXP is specified by the license key, but cannot exceed the original hardware restrictions:
|
...