aries.5 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

ARIES(5) ARIES(5)

(HP Integrity Systems Only)

NAME

ARIES, aries - dynamically and transparently execute PA-RISC HP-UX applications on Integrity systems

running HP-UX

DESCRIPTION

ARIES is a dynamic binary translator which transparently executes 32-bit and 64-bit PA-RISC HP-UX

applications on Integrity systems running HP-UX. The name

ARIES expands to Automatic Recompila-

tion and

Integrated Environment Simulation.

ARIES consists of the following four shared libraries:

/usr/lib/hpux32/pa_boot32.so

/usr/lib/hpux32/aries32.so

/usr/lib/hpux64/pa_boot64.so

/usr/lib/hpux64/aries64.so

aries32.so is the shared library that contains the ARIES dynamic translator for 32-bit applications.

pa_boot32.so is the dynamic loader for aries32.so

. Likewise, aries64.so and

pa_boot64.so are the 64-bit ARIES components.

The HP-UX operating system kernel on Integrity systems recognizes PA-RISC HP-UX executables and

invokes ARIES to dynamically translate and execute the application. For 32-bit PA-RISC HP-UX execut-

ables, the Integrity HP-UX kernel invokes

pa_boot32.so, which loads aries32.so into memory,

relocates it and sets up internal memory segments. aries32.so starts emulation at the program entry

point. Likewise, pa_boot64.so and aries64.so are loaded for 64-bit PA-RISC HP-UX executables.

ARIES consists of two major sub-systems:

• Instruction Set Architecture (ISA) emulation engine

• Environment emulation engine

The ISA emulation engine is comprised of a fast interpreter and a dynamic translator. The interpreter

emulates one instruction at a time. After a sufﬁcient number of iterations over a PA-RISC basic block,

the dynamic translator is invoked to translate the basic block into functionally equivalent IA64 native

code, which is stored in translation buffer. Subsequent references to translated basic blocks do not

require further interpretation or translation.

The environment emulation engine is responsible for the emulation of PA-RISC application’s system calls,

signal delivery, threads management. Interactions among various ARIES sub-systems are controlled and

facilitated by the control system, which also keeps mapping between the PA-RISC application’s basic

block and the translated code block addresses.

PA-RISC HP-UX GDB DEBUGGING SUPPORT

ARIES supports debugging of PA-RISC HP-UX applications on Integrity systems running HP-UX using

the PA-RISC HP-UX

gdb, the GNU debugger.

On Integrity HP-UX systems,

/usr/ccs/bin contains the PA-RISC gdb32 and gdb64 executables. A

symbolic link named /usr/ccs/bin/gdbpa points to /usr/ccs/bin/gdb32

. The Integrity HP-UX

system’s

gdb debugger recognizes the PA-RISC executable being debugged and launches

/usr/ccs/bin/gdbpa under ARIES.

Debugging PA-RISC Applications on Integrity Systems

Use the following steps to debug PA-RISC HP-UX applications on Integrity HP-UX systems using

PA-RISC

gdb:

1. Set the environment variable

PA_DEBUG to 1.

2. Set the environment variable

SHELL to point to a PA-RISC shell, copied from a PA-RISC HP-UX sys-

tem from /usr/bin path.

3. Add

/usr/ccs/bin to the PATH environment variable.

4. Invoke

gdb as:

gdb PA-RISC_executable

NOTE: Make sure that the user has write permission on /tmp directory and that there is enough space

to create a temporary ﬁle of one page size as obtained by sysconf(_SC_PAGE_SIZE) system call.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (16 pages)

PAGE 1
ARIES(5) ARIES(5) (HP Integrity Systems Only) NAME ARIES, aries - dynamically and transparently execute PA-RISC HP-UX applications on Integrity systems running HP-UX DESCRIPTION ARIES is a dynamic binary translator which transparently executes 32-bit and 64-bit PA-RISC HP-UX applications on Integrity systems running HP-UX. The name ARIES expands to Automatic Recompilation and Integrated Environment Simulation. ARIES consists of the following four shared libraries: A /usr/lib/hpux32/pa_boot32.
PAGE 2
ARIES(5) ARIES(5) (HP Integrity Systems Only) The rest of the debugging operations are the same as that on the PA-RISC HP-UX platform. All commands of the gdb debugger are supported subject to limitations listed under the Limitations of PA-RISC GDB Support section in this manpage. Attaching PA-RISC GDB to PA-RISC process under ARIES An already running PA-RISC process can be debugged on Integrity systems by attaching PA-RISC debugger gdb, using following steps: A aA 1.
PAGE 3
ARIES(5) ARIES(5) (HP Integrity Systems Only) NOTES: ARIES HP-UX 11i Version 3 1. As per the default core file format on HP-UX 11i Version 3, ARIES generates PA-RISC application core file in new format using large utsname structure. See uname(2) for more details on the large utsname structure. You need to use latest version of tools like gdb to work with new format core file. Use the ARIES option -core_format to generate PA-RISC application core files in the old format.
PAGE 4
ARIES(5) ARIES(5) (HP Integrity Systems Only) • Patterns of type /opt/all/*foo* and */*/foo which have more than one wild card in directory part or application name part are not allowed. NOTE: In above points foo is only an example and not an actual pattern.
PAGE 5
ARIES(5) ARIES(5) (HP Integrity Systems Only) with release version of the Integrity HP-UX systems. Disabling (-nocompat_core) this option flag will result in core files which may not work with gdb from an older PA-RISC HP-UX (11i version 1 and earlier) platform. Such core files need to be debugged using gdb from PA-RISC HP-UX 11i version 2 and later. The default state of this option flag is enabled (-compat_core).
PAGE 6
ARIES(5) ARIES(5) (HP Integrity Systems Only) The default state of this option flag is enabled (-opt_fpgr). -[no]opt_reorder [Disables] enables the ARIES optimizations for dynamically translated code to re-order PA-RISC state changing instructions, loads, and updates to general registers in order to achieve better scheduling of translated code.
PAGE 7
ARIES(5) ARIES(5) (HP Integrity Systems Only) Value Default: Max: Min: 32-bit ARIES 2048 KB (2 MB) 4096 KB (4 MB) 512 KB 64-bit ARIES 2048 KB (2 MB) 4096 KB (4 MB) 512 KB -ap_heap_ssz { size | default } Size in kbytes of the memory area used for the ARIES private heap. This area is part of the ARIES heap whose size is determined by the ARIES option -heap_ssz. This area is used for ARIES’s internal malloc() calls.
PAGE 8
ARIES(5) ARIES(5) (HP Integrity Systems Only) -descsz { size | default } Size in kbytes of the memory area for ARIES internal data structures (code cache descriptors) for accessing and managing translated code blocks.
PAGE 9
ARIES(5) ARIES(5) (HP Integrity Systems Only) WARNING: Using this option may cause the application to fail if the application and any of its dependent shared libraries changed from the time the translations were saved previously. -nomore Enable ARIES to stop further processing of options after executing this option. The processing is stopped from any ARIES RC file down through the search path.
PAGE 10
ARIES(5) ARIES(5) (HP Integrity Systems Only) Example: ARIES Resource Configuration File To execute a 32-bit PA-RISC application hello_world through ARIES using 32 MB of stack, you can place an .ariesrc file containing the following line in user’s home directory or in the root (/) directory.
PAGE 11
ARIES(5) ARIES(5) (HP Integrity Systems Only) 7. Memory area used by ARIES dynamic translator as heap. Memory allocation from AMA happens dynamically on demand. A PA-RISC process running under ARIES will have larger memory footprint (resident memory) as compared to native PA-RISC system. The increase in process resident memory size depends on actual memory allocated from AMA.
PAGE 12
ARIES(5) ARIES(5) (HP Integrity Systems Only) Maximum Number of Threads A PA-RISC application can create a maximum of 85 threads under 32-bit ARIES and 438 threads under 64-bit ARIES with the default values of ARIES options and the kernel tunable parameters, pa_maxssiz_32bit and pa_maxssiz_64bit . Make sure that the kernel tunable parameter max_thread_proc value is sufficiently large to create the required number of threads.
PAGE 13
ARIES(5) ARIES(5) (HP Integrity Systems Only) NOTE: Stack sizes can be inherited among Integrity system native processes (32-bit and 64-bit) and emulated PA-RISC processes (32-bit and 64-bit), subjected to the limitation on available stack space under ARIES.
PAGE 14
ARIES(5) ARIES(5) (HP Integrity Systems Only) ARIES Performance Tuning Users may find following tips useful for tuning the performance of their PA-RISC applications under ARIES: A aA 1. For applications which are very much loop intensive, reduce the ARIES translation threshold value (ARIES option -ts). 2.
PAGE 15
ARIES(5) ARIES(5) (HP Integrity Systems Only) 4. ARIES does not guarantee correct emulation of PA-RISC applications which make assumptions about "time taken to execute certain parts of application code and/or system calls". Such applications are theoretically non-synchronized applications, and hence, need to be corrected with proper synchronization techniques using mutex locks and/or semaphores. 5. ARIES does not support applications that use ptrace() or profil() system calls.
PAGE 16
(Notes) A (Notes) aA 16 Hewlett-Packard Company −1− HP-UX 11i Version 3: September 2010