Aries man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

ARIES(5)							      ARIES(5)

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 run‐
       ning HP-UX.  The name expands to and

       ARIES consists of the following four shared libraries:

	      is  the  shared
	      library	 that
	      contains	  the
	      ARIES dynamic
	      translator  for 32-bit
	      applications.  is	 the
	      dynamic	loader	 for
	      Likewise, and are	 the
	      64-bit   ARIES  compo‐
	      nents.

       The  HP-UX  operating  system
       kernel  on  Integrity systems
       recognizes PA-RISC HP-UX exe‐
       cutables and invokes ARIES to
       dynamically   translate	 and
       execute the application.	 For
       32-bit PA-RISC HP-UX executa‐
       bles,   the  Integrity  HP-UX
       kernel  invokes	which  loads
       into memory, relocates it and
       sets up internal memory	seg‐
       ments.	starts	emulation at
       the  program   entry   point.
       Likewise,  and are loaded for
       64-bit PA-RISC HP-UX executa‐
       bles.

       ARIES  consists	of two major
       sub-systems:

	      ·	 Instruction	 Set
		 Architecture  (ISA)
		 emulation engine

	      ·	 Environment  emula‐
		 tion engine

       The  ISA	 emulation engine is
       comprised of  a	fast  inter‐
       preter and a dynamic transla‐
       tor.   The  interpreter	emu‐
       lates  one  instruction	at a
       time.   After  a	  sufficient
       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 interpre‐
       tation or translation.

       The   environment   emulation
       engine is responsible for the
       emulation of PA-RISC applica‐
       tion's system  calls,  signal
       delivery, threads management.
       Interactions  among   various
       ARIES  sub-systems  are	con‐
       trolled	and  facilitated  by
       the   control  system,  which
       also  keeps  mapping  between
       the   PA-RISC   application's
       basic block  and	 the  trans‐
       lated 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
       the GNU debugger.

       On  Integrity  HP-UX systems,
       contains the PA-RISC and exe‐
       cutables.   A  symbolic	link
       named points to The Integrity
       HP-UX  system's debugger rec‐
       ognizes	the   PA-RISC	exe‐
       cutable	being  debugged	 and
       launches under ARIES.

   Debugging PA-RISC Applications on
       Integrity Systems
       Use  the	 following  steps to
       debug PA-RISC HP-UX  applica‐
       tions on Integrity HP-UX sys‐
       tems using PA-RISC

       1.  Set the environment vari‐
	   able to 1.

       2.  Set the environment vari‐
	   able	 to   point   to   a
	   PA-RISC   shell,   copied
	   from a PA-RISC HP-UX sys‐
	   tem from path.

       3.  Add	to  the	 environment
	   variable.

       4.  Invoke as:

	   $

       NOTE: Make sure that the user
       has   write   permission	  on
       directory and that  there  is
       enough space to create a tem‐
       porary file of one page	size
       as obtained by system call.

       The  rest  of  the  debugging
       operations are  the  same  as
       that  on	 the  PA-RISC  HP-UX
       platform.   All	commands  of
       the  debugger  are  supported
       subject to limitations listed
       under  the  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 attach‐
       ing  PA-RISC  debugger  using
       following steps:

       1.  Perform  the	 preparatory
	   steps as described  above
	   for	 debugging   PA-RISC
	   application	under  ARIES
	   using PA-RISC

       2.  Invoke as follows:

	   $

       After  debugging is finished,
       perform the following steps.

       1.  Unset   the	 environment
	   variable

       2.  Restore    the   original
	   value of the	 environment
	   variable.

   Limitations	of  PA-RISC GDB Sup‐
       port
       The  limitations	 of  PA-RISC
       emulation  under ARIES are as
       follows:

       1.  No support for  debuggers
	   other  than PA-RISC HP-UX
	   for	 debugging   PA-RISC
	   applications on Integrity
	   systems.

       2.  No support for  old	ver‐
	   sions (of HP-UX 10.20 and
	   earlier).	    However,
	   debugging  of HP-UX 10.20
	   applications	  using	   a
	   HP-UX  11.0	(and  newer)
	   PA-RISC is supported.

       3.  PA-RISC  behaves  differ‐
	   ently for child processes
	   created using and  system
	   calls.    ARIES  emulates
	   and system calls  identi‐
	   cally.   The exact behav‐
	   ior	shown	by   PA-RISC
	   under  ARIES	 may  differ
	   from	 that  on  a  native
	   PA-RISC HP-UX system.

       4.  If  the  debugged process
	   is blocking in  a  system
	   call,  any attempt to get
	   to the command prompt  by
	   pressing  does  not work.
	   The process needs  to  be
	   killed  from	 a different
	   shell.

       5.  ARIES  does	not  provide
	   true	  emulation  of	 MxN
	   threads,  and  thus	does
	   not	support debugging of
	   PA-RISC applications that
	   are	linked with pthreads
	   library    and     create
	   threads in MxN model.

	   NOTE:  The PA-RISC appli‐
	   cations linked  with	 MxN
	   pthreads library are emu‐
	   lated under ARIES as tra‐
	   ditional 1x1 threads, and
	   thus can only be debugged
	   under  ARIES as any other
	   non-MxN    multi-threaded
	   application.	   Refer  to
	   the section in this	man‐
	   page	 for  more  informa‐
	   tion.

       6.  ARIES supports  debugging
	   of	32-bit	 and  64-bit
	   PA-RISC  HP-UX   applica‐
	   tions     using    32-bit
	   PA-RISC   HP-UX    64-bit
	   PA-RISC HP-UX is not sup‐
	   ported under ARIES.

   Generation of PA-RISC HP-UX	Com‐
       patible Core File
       ARIES  supports	creation  of
       PA-RISC HP-UX compatible core
       files  on  Integrity systems.
       The size of the core file  is
       limited	 by  and/or  values.
       See   ulimit(2)	 and   setr‐
       limit(2).

       The  PA-RISC application core
       file generated by ARIES	will
       have the name as

       The PA-RISC HP-UX debugger is
       required to debug application
       core  file generated by ARIES
       on   an	 Integrity   system.
       Alternately,   the   applica‐
       tion's  core  file   can	  be
       transferred to a PA-RISC sys‐
       tem  and	 debugged  using   a
       PA-RISC	debugger.   Refer to
       help on the command.

       After ARIES has	successfully
       written	a  core file for the
       PA-RISC application, it	will
       print  the  following message
       on

       If the resulting core file is
       named  as  or  it  will be an
       ARIES core file,	 not  useful
       for application debugging.

       The  ARIES-generated  PA-RISC
       HP-UX compatible core file is
       recognized  by the command on
       PA-RISC and  Integrity  HP-UX
       systems.	 See file(1).

       1.  As  per  the default core
	   file format on HP-UX	 11i
	   Version  3,	ARIES gener‐
	   ates 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 to
	   work with new format core
	   file.

	   Use	the  ARIES option to
	   generate PA-RISC applica‐
	   tion	 core  files  in the
	   old format.	Refer to the
	   section  in	this manpage
	   for more information.

       2.  If the core file  pattern
	   and	settings  have	been
	   modified  by	 the  system
	   call or by settings, then
	   ARIES  will	follow	 the
	   same	   naming    pattern
	   instead  of	writing	 the
	   application	core file to
	   Refer to  coreadm(2)	 and
	   init(1M).

ARIES  RESOURCE	 CONFIGURATION	(RC)
       FILE:  PASSING	OPTIONS	  TO
       ARIES
       Options	to  ARIES are passed
       through a resource configura‐
       tion (RC) file.

       ·  For 32-bit ARIES, resource
	  configuration file name is

       ·  For 64-bit ARIES, resource
	  configuration file name is

       Refer  to the section in this
       manpage for details on  loca‐
       tion  and  search  order	 for
       ARIES resource  configuration
       file.

   ARIES Resource Configuration File
       Format
       The ARIES resource configura‐
       tion  file may contain multi‐
       ple lines each with the	fol‐
       lowing format:

	       <full-path-of-PA-RISC-application1> <aries-options>
	       <full-path-of-PA-RISC-application2> <aries-options>
	       <PA-RISC-application3-path-with-wild-cards> <aries-options>
	       ...
	       ...

       Refer  to the section in this
       manpage for examples on ARIES
       resource configuration file.

   ARIES Resource Configuration File
       Processing Rules
       1.  Application path name and
	   ARIES   options  must  be
	   separated by one or	more
	   white spaces.

       2.  Each	 non empty line must
	   begin from first column.

       3.  ARIES  options   may	  be
	   specified   for  multiple
	   applications, each begin‐
	   ning on a separate line.

       4.  Relative  paths and shell
	   variables	 are	 not
	   allowed.

       5.  An  invalid	ARIES option
	   will	 result	 in  process
	   termination with error.

       6.  in	 first	 column	  is
	   treated  as	comment	 and
	   rest	  of   the  line  is
	   ignored.

       7.  is treated as  wild	card
	   character and can be used
	   in application path name.

       8.  ARIES wild card  matching
	   is  based  on simple text
	   pattern  match  with	  no
	   expansion of directory or
	   file name.

       9.  When using wild cards  it
	   is  possible for multiple
	   lines to match  the	cur‐
	   rent	  application.	  If
	   this	 behavior   is	 not
	   expected,   then   change
	   your ARIES resource	con‐
	   figuration  file  accord‐
	   ingly.

       10. Application	 path	name
	   field must be one of fol‐
	   lowing:

	   ·  Full absolute path  of
	      PA-RISC	 application
	      executable.

	   ·  Root  directory  ARIES
	      options  on  this line
	      will be applied to all
	      PA-RISC  processes  on
	      the system.

	   ·  PA-RISC	 application
	      path with wild cards

	      ·	 There	can  be only
		 one  wild  card  in
		 directory  path and
		 executable	name
		 each.

	      ·	 More  than one wild
		 card in either part
		 of   the   pathname
		 will	result	  in
		 process termination
		 with error.

	      ·	 Valid examples	 are
		 of   such  patterns
		 as: and

	      ·	 Patterns  of	type
		 and which have more
		 than one wild	card
		 in  directory	part
		 or application name
		 part	  are	 not
		 allowed.

		 NOTE:	 In    above
		 points	 is  only an
		 example and not  an
		 actual pattern.

   ARIES RC File Search Path
       ARIES	searches   for	 the
       resource	 configuration	(RC)
       file  in	 the following loca‐
       tions in the following order:

	      ·	 Root directory sys‐
		 tem  wide  ARIES RC
		 file

	      ·	 Application  direc‐
		 tory:	all directo‐
		 ries  in  the	full
		 absolute   path  of
		 the PA-RISC  appli‐
		 cation

	      ·	 User's	 home direc‐
		 tory	(value	  of
		 environment   vari‐
		 able

       In regards to  the  ARIES  RC
       file  search,  here are a few
       points:

       1.  ARIES  option  processing
	   is  additive	 in  nature.
	   ARIES continues to search
	   the RC file in all search
	   paths.    ARIES   options
	   found  in earlier RC file
	   matches  are	 overwritten
	   by option values in later
	   RC file matches.

       2.  If the value of  environ‐
	   ment	 variable  is or the
	   path is  not	 accessible,
	   ARIES   will	 ignore	 the
	   user's private RC file.

       3.  If ARIES cannot  find  or
	   access the RC file in any
	   of the search  paths,  it
	   will	    continue	with
	   default     values	  of
	   options.

       4.  The	ARIES RC file search
	   in  application  directo‐
	   ries	 enables application
	   vendors  to	ship  custom
	   ARIES RC files with ARIES
	   options  values  suitable
	   for	  their	  particular
	   applications.

   Advanced ARIES Options
       Most PA-RISC applications run
       as  expected under ARIES with
       the   default	values	  of
       options.	 The following ARIES
       options	 are   useful	 for
       advanced	 users	who may want
       to  control  ARIES   resource
       management   and/or  to	tune
       ARIES   for   their   PA-RISC
       applications.

	      ·	 To  enable  or dis‐
		 able  ARIES  option
		 flags	you  do	 not
		 need to specify  or
		 keywords.	Such
		 ARIES option  flags
		 have optional nega‐
		 tion with added  at
		 the   beginning  of
		 the  ARIES   option
		 name.

		 For  example,	will
		 enable	  and	will
		 disable strong mem‐
		 ory   ordering	  in
		 ARIES.

	      ·	 Certain       ARIES
		 options       which
		 expect numeric val‐
		 ues may be passed a
		 case	 insensitive
		 keyword  to   reset
		 the   corresponding
		 option	  value	  to
		 ARIES	     default
		 value.

	      ·	 ARIES options which
		 require  a  numeric
		 value in kbytes for
		 size do not require
		 kbytes keyword.

		 For   example,	  is
		 valid	and  or	 are
		 not valid, and will
		 result in an error.

	      ·	 is   part   of	 the
		 ARIES option format
		 and  must be speci‐
		 fied.

       [Disables]
		 enables  the	cre‐
		 ation	of  separate
		 address  map	data
		 structure	 for
		 dynamically  gener‐
		 ated	  code	  by
		 PA-RISC    applica‐
		 tion.	    Enabling
		 this  option	flag
		 may provide optimal
		 performance	 for
		 JVM-like   applica‐
		 tions.

		 The  default  state
		 of this option flag
		 is enabled

       [Disables]
		 enables the dynamic
		 patching  of branch
		 targets  in   ARIES
		 translated	code
		 blocks.

		 WARNING:  Disabling
		 this	option	flag
		 will cause signifi‐
		 cant	 performance
		 slowdown.

		 The  default  state
		 of this option flag
		 is enabled

       [Disables]
		 enables the  sched‐
		 uling and optimiza‐
		 tion	 of    ARIES
		 translated    code.
		 Enabling	this
		 option flag is use‐
		 ful only for reduc‐
		 ing	the    ARIES
		 dynamic translation
		 time  although	 the
		 overall performance
		 may become slower.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the genera‐
		 tion	of   PA-RISC
		 application	core
		 file with  OS	ver‐
		 sion  field  filled
		 with  release	ver‐
		 sion	  of	 the
		 Integrity     HP-UX
		 systems.  Disabling
		 this  option	flag
		 will result in core
		 files which may not
		 work  with  from an
		 older PA-RISC HP-UX
		 (11i  version 1 and
		 earlier)  platform.
		 Such	core   files
		 need to be debugged
		 using	from PA-RISC
		 HP-UX 11i version 2
		 and later.

		 The  default  state
		 of this option flag
		 is enabled

       [Disables]
		 enables   appending
		 of the	 process  ID
		 to    the   PA-RISC
		 application	core
		 file	name.	 See
		 also getpid(2).

		 If this option flag
		 is enabled the core
		 file name will be

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the dynamic
		 translation	  of
		 PA-RISC       basic
		 blocks	 that access
		 and   modify	 the
		 Floating      Point
		 Acess Regiser (FPSR
		 : fr0L) frequently.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables  the print‐
		 ing	of     ARIES
		 options  and  their
		 minimum,   maximum,
		 and  default values
		 on If	this  option
		 flag	is   enabled
		 ARIES	 will	exit
		 after	printing the
		 available options.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the genera‐
		 tion	 of   memory
		 fence	 instruction
		 in  translation for
		 ordered      memory
		 operations	  of
		 PA-RISC    applica‐
		 tion.

		 WARNING:   Enabling
		 this  option	flag
		 will  slow down the
		 performance of mem‐
		 ory  loads in ARIES
		 translated    code.
		 Enable	 this option
		 flag  only  if	 the
		 PA-RISC application
		 expecting    strong
		 memory	    ordering
		 (program uses vari‐
		 ables)	 fails under
		 ARIES.

		 NOTE: Enabling	 the
		 ARIES	option	flag
		 does not  automati‐
		 cally	enable	this
		 option flag.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the minimum
		 memory	   footprint
		 (process   resident
		 memory	 size) under
		 ARIES.	    Enabling
		 this option flag is
		 useful for applica‐
		 tions	 that	have
		 constraints	  on
		 process      memory
		 footprint.  If this
		 option	   flag	  is
		 enabled  the  sizes
		 of all ARIES memory
		 segments are set to
		 their	minimum val‐
		 ues.

		 WARNING:   Enabling
		 this	option	flag
		 may  cause  perfor‐
		 mance	slowdown due
		 to increased number
		 of  ARIES  transla‐
		 tion  code   buffer
		 flushes.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables  the strong
		 memory ordering  in
		 ARIES.	  You should
		 enable this  option
		 flag only when your
		 PA-RISC application
		 expecting    strong
		 memory	    ordering
		 fails	under ARIES.
		 Such an application
		 would	be  the one,
		 which does not	 use
		 memory	    ordering
		 semantics like com‐
		 pleter	 in instruc‐
		 tions	or  cast  in
		 high	level  code,
		 and  still  expects
		 strong	      memory
		 ordering.

		 WARNING:   Enabling
		 this	option	flag
		 may   cause   2x-3x
		 performance   slow‐
		 down.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the mapping
		 of  the emulated FP
		 (Floating    Point)
		 register context on
		 general    register
		 stack.	 The perfor‐
		 mance of the float‐
		 ing point intensive
		 PA-RISC    applica‐
		 tions may be better
		 if this option flag
		 is enabled

		 The  default  state
		 of this option flag
		 is enabled

       [Disables]
		 enables  the  ARIES
		 optimizations	 for
		 dynamically  trans‐
		 lated code  to	 re-
		 order PA-RISC state
		 changing   instruc‐
		 tions,	 loads,	 and
		 updates to  general
		 registers  in order
		 to  achieve  better
		 scheduling	  of
		 translated code.

		 WARNING:   Do	 not
		 enable	 this option
		 flag  with   multi-
		 threaded   applica‐
		 tions	 like	 JVM
		 which	expect	pre‐
		 cise  delivery	  of
		 synchronous  excep‐
		 tions and  register
		 updates.	Such
		 applications	 may
		 crash	 with	core
		 file if this option
		 flag is enabled

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables  the emula‐
		 tion  of  the	 and
		 system	  calls,  to
		 return	 information
		 specific  to native
		 PA-RISC HP-UX	sys‐
		 tems.	See uname(2)
		 and sysconf(2).

		 Enable this  option
		 flag  only  if	 the
		 PA-RISC application
		 expects  the return
		 values of and	sys‐
		 tem  calls,  to  be
		 specific   to	 the
		 values	 that  would
		 have been  obtained
		 if  the application
		 was   running	  on
		 PA-RISC  HP-UX sys‐
		 tem.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables  the  trace
		 scheduling  and low
		 level	optimization
		 of ARIES translated
		 code.

		 NOTE: Enabling this
		 option	  flag	 may
		 provide    improved
		 performance	 for
		 compute   intensive
		 applications.

		 The  default  state
		 of this option flag
		 is disabled

       [Disables]
		 enables the dynamic
		 translation	  in
		 ARIES.	   Disabling
		 this option flag is
		 useful	  only	 for
		 triaging of dynamic
		 translator    fail‐
		 ures.

		 WARNING:  Disabling
		 this	option	flag
		 will cause signifi‐
		 cant	 performance
		 slowdown.

		 The  default  state
		 of this option flag
		 is enabled

       [Disables]
		 enables the dynamic
		 translation of self
		 modifying  (dynami‐
		 cally	  generated)
		 code.	   Disabling
		 this option flag is
		 useful	  only	 for
		 triaging  of  Java-
		 based	 application
		 failures      under
		 ARIES.

		 WARNING:  Disabling
		 this	option	flag
		 will cause signifi‐
		 cant	 performance
		 slowdown for  Java-
		 based applications.

		 The  default  state
		 of this option flag
		 is enabled

       Size  in	 kbytes of the total
       memory area to  be  used	 for
       ARIES
		 address  map (AMAP)
		 data	 structures,
		 for	    mappings
		 between     PA-RISC
		 basic	 blocks	 and
		 translated	code
		 addresses.

		 Value		32-bit ARIES	   64-bit ARIES
		 ───────────────────────────────────────────────
		 Default:   16384 KB (16 MB)   24576 KB (24 MB)
		 Max:	    65536 KB (64 MB)   98304 KB (96 MB)
		 Min:	     8192 KB ( 8 MB)	8192 KB ( 8 MB)

		 NOTE:	To  minimize
		 the	 performance
		 drop	  due	  to
		 increased frequency
		 of  ARIES AMAP area
		 overflow, HP recom‐
		 mends	setting this
		 option value at the
		 default  or maximum
		 size.

		 For optimal perfor‐
		 mance,	 a  ratio of
		 1:2:2	 should	  be
		 maintained  for the
		 values of the ARIES
		 options: and

       Size  in kbytes of the memory
       area used for  ARIES  address
       map (AMAP) data
		 structures   corre‐
		 sponding to dynamic
		 translations	  of
		 self modifying code
		 of PA-RISC applica‐
		 tion.	This area is
		 part  of the memory
		 region	 whose	size
		 is   determined  by
		 the ARIES option

		 Value	      32-bit ARIES     64-bit ARIES
		 ───────────────────────────────────────────
		 Default:   2048 KB (2 MB)   2048 KB (2 MB)
		 Max:	    4096 KB (4 MB)   4096 KB (4 MB)
		 Min:	     512 KB		     512 KB

       Size in kbytes of the  memory
       area  used for the ARIES pri‐
       vate heap.
		 This area  is	part
		 of  the  ARIES heap
		 whose	  size	  is
		 determined  by	 the
		 ARIES	option	This
		 area  is  used	 for
		 ARIES's    internal
		 calls.

		 Value		  32-bit ARIES	       64-bit ARIES
		 ───────────────────────────────────────────────────
		 Default:	4096 KB (4 MB)	     8192 KB (8 MB)
		 Max:	    heap_ssz - 1024 KB	 heap_ssz - 2048 KB
		 Min:		1024 KB (1 MB)	     2048 KB (2 MB)

		 Increase  the value
		 of    this    ARIES
		 option if the ARIES
		 error is or

       Size in kbytes of the backing
       store  area  for ARIES native
       threads that are
		 created for  emula‐
		 tion  of the appli‐
		 cation's threads.

		 Value	    32-bit ARIES   64-bit ARIES
		 ───────────────────────────────────────
		 Default:	   48 KB	  48 KB
		 Max:		   64 KB	  64 KB
		 Min:		   48 KB	  48 KB

       Size in kbytes of the  memory
       stack  area  for ARIES native
       threads that are
		 created for  emula‐
		 tion  of the appli‐
		 cation's threads.

		 Value	    32-bit ARIES   64-bit ARIES
		 ───────────────────────────────────────
		 Default:	  160 KB	 160 KB
		 Max:		  256 KB	 256 KB
		 Min:		  128 KB	 128 KB

       Size in kbytes of  the  ARIES
       translated code buffer.

		 Value		32-bit ARIES	   64-bit ARIES
		 ───────────────────────────────────────────────
		 Default:   16384 KB (16 MB)   16384 KB (16 MB)
		 Max:	    65536 KB (64 MB)   65536 KB (64 MB)
		 Min:	     4096 KB ( 4 MB)	4096 KB ( 4 MB)

		 NOTE:	To  minimize
		 the	 performance
		 drop	  due	  to
		 increased frequency
		 of ARIES code cache
		 area  overflow,  HP
		 recommends  setting
		 this  option  value
		 at default or maxi‐
		 mum.

		 For optimal perfor‐
		 mance,	 a  ratio of
		 1:2:2	 should	  be
		 maintained  for the
		 values of the ARIES
		 options: and

       Format of the ARIES generated
       PA-RISC	 application	core
       files.
		 By  default,  ARIES
		 generates core file
		 with  large  struc‐
		 ture.	  Use	this
		 option	 to generate
		 PA-RISC application
		 core file in format
		 other	 than	 the
		 default.

		 The   valid  values
		 for version are  as
		 follows:

		 old  core file for‐
		 mat: with old
		      structure.

		 new core file	for‐
		 mat: with large
		      structure.  is
		      the    default
		      value.

		 Refer	to  the sec‐
		 tion in  this	man‐
		 page for details on
		 core file formats.

       Size in kbytes of the  memory
       area  for ARIES internal data
       structures (code
		 cache	descriptors)
		 for  accessing	 and
		 managing translated
		 code blocks.

		 Value		32-bit ARIES	   64-bit ARIES
		 ───────────────────────────────────────────────
		 Default:    8192 KB ( 8 MB)	8192 KB ( 8 MB)
		 Max:	    32768 KB (32 MB)   65536 KB (64 MB)
		 Min:	     4096 KB ( 4 MB)	4096 KB ( 4 MB)

		 NOTE:	To  minimize
		 the	 performance
		 drop	  due	  to
		 increased frequency
		 of ARIES code cache
		 descriptor	area
		 overflow, HP recom‐
		 mends setting	this
		 option	  value	  at
		 default or maximum.

		 For optimal perfor‐
		 mance,	 a  ratio of
		 1:2:2	 should	  be
		 maintained  for the
		 values of the ARIES
		 options: and

       Size  in kbytes of the memory
       area  for   shared   use	  by
       dynamic translator
		 internal     memory
		 allocation	 and
		 alternate     ARIES
		 heap	for   memory
		 allocation   during
		 signal handling.

		 Value	      32-bit ARIES	 64-bit ARIES
		 ─────────────────────────────────────────────
		 Default:   5120 KB (5 MB)    8192 KB ( 8 MB)
		 Max:	    8192 KB (8 MB)   16384 KB (16 MB)
		 Min:	    5120 KB (5 MB)    5120 KB ( 5 MB)

       Size in kbytes of  the  ARIES
       heap used for ARIES's own
		 calls	and to allo‐
		 cate	space	 for
		 ARIES	thread	cre‐
		 ation.

		 The ARIES  heap  is
		 divided   into	 two
		 parts.	  The  first
		 part	is  used  as
		 ARIES private	heap
		 whose	  size	  is
		 determined  by	 the
		 option	 The remain‐
		 ing area  from	 the
		 ARIES	heap is used
		 to allocate  memory
		 for	 the	 new
		 threads.

		 Value		32-bit ARIES	     64-bit ARIES
		 ─────────────────────────────────────────────────
		 Default:   22528 KB (22 MB)   131072 KB (128 MB)
		 Max:		    variable		 variable
		 Min:	     8192 KB ( 8 MB)	16384 KB ( 16 MB)

		 The  values   above
		 are  shown with the
		 default  values  of
		 kernel	     tunable
		 parameters,
		 pa_maxssiz_32bit
		 and	    pa_maxs‐
		 siz_64bit,	 for
		 32-bit	 and  64-bit
		 ARIES respectively.

		 With increased val‐
		 ues of the  respec‐
		 tive kernel tunable
		 parameters,	 the
		 maximum   value  of
		 ARIES heap is	com‐
		 puted as follows:

		 ·
		    Max
		    heap_ssz=pa_maxs‐
		    siz_32bit-ssz-
		    ccsz-amapsz-
		    descsz-
		    exc_dynt_heap_ssz-5
		    MB

		 ·
		    Max
		    heap_ssz=pa_maxs‐
		    siz_64bit-ssz-
		    ccsz-amapsz-
		    descsz-
		    exc_dynt_heap_ssz-24
		    MB

       Size  in	 kbytes	 of the ini‐
       tially  allocated  stack	 for
       PA-RISC applications.

		 Value	    32-bit ARIES   64-bit ARIES
		 ───────────────────────────────────────
		 Default:	   64 KB	  64 KB
		 Max:	       ssz value      ssz value
		 Min:		   32 KB	  32 KB

		 At  process startup
		 time,	ARIES	com‐
		 putes	the  minimum
		 value of by  adding
		 the  sizes of argu‐
		 ment strings, envi‐
		 ronment    variable
		 strings,  and	key‐
		 bits structure.  If
		 the computed  value
		 is   greater	than
		 value,	 then  ARIES
		 increases	this
		 value accordingly.

       Load the	 dynamically  trans‐
       lated code from
		 file_name	  at
		 process     startup
		 time.	 This option
		 can optimize  ARIES
		 time	 spent	  in
		 dynamic    transla‐
		 tions.	   Refer  to
		 the   option	 for
		 storing  the  ARIES
		 dynamic    transla‐
		 tions to a file.

		 WARNING: Using this
		 option	 may   cause
		 the  application to
		 fail if the  appli‐
		 cation	 and  any of
		 its	   dependent
		 shared	   libraries
		 changed  from	 the
		 time  the  transla‐
		 tions	were   saved
		 previously.

       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.

		 This option enables
		 application vendors
		 to lock  the  ARIES
		 configuration	  in
		 ARIES	 RC    files
		 shipped  as part of
		 the	 application
		 installation.

       Chunk   size  in	 kbytes	 for
       incremental memory allocation
       in ARIES for
		 PA-RISC application
		 stack, ARIES  heap,
		 ARIES	code  cache,
		 descriptors   stack
		 and AMAP regions.

		 Value	    32-bit ARIES   64-bit ARIES
		 ───────────────────────────────────────
		 Default:	   64 KB	  64 KB
		 Max:		 1024 KB	1024 KB
		 Min:		    4 KB	   4 KB

		 WARNING: A very low
		 value	 for	this
		 option	       might
		 degrade     overall
		 system	 performance
		 due  to  too	many
		 mapped regions.

       Reset to default values.	 All
       ARIES  options  processed  so
       far
		 from  any  ARIES RC
		 file prior to	this
		 option are reset to
		 their default	val‐
		 ues.

       Save  ARIES  dynamic transla‐
       tions to
		 file_name	  at
		 process exit.	Such
		 saved	translations
		 may   be  used	 for
		 later	 invocations
		 of  the same appli‐
		 cation using  ARIES
		 option

       Size  in kbytes of the memory
       area for	 allocating  PA-RISC
       application stack.

		 Value		  32-bit ARIES		 64-bit ARIES
		 ─────────────────────────────────────────────────────
		 Default:     8192 KB (	 8 MB)	  262144 KB ( 256 MB)
		 Max:	    384000 KB (383 MB)	 2097152 KB (2048 MB)
		 Min:	       256 KB			       256 KB

		 The  default values
		 shown	 above	 are
		 with	the  default
		 values of the	ker‐
		 nel tunable parame‐
		 ters,	    pa_maxs‐
		 siz_32bit	 and
		 pa_maxssiz_64bit,
		 for	32-bit	 and
		 64-bit	       ARIES
		 respectively.

		 To   increase	 the
		 size	of   PA-RISC
		 stack	 beyond	 the
		 default  values  as
		 shown	 above	 you
		 must  increase	 the
		 kernel	     tunable
		 parameters,
		 pa_maxssiz_32bit
		 and	    pa_maxs‐
		 siz_64bit,	 for
		 32-bit	 and  64-bit
		 ARIES respectively.

		 Use  this option to
		 override the  ARIES
		 assumed  stack size
		 for PA-RISC  appli‐
		 cation.   Refer  to
		 the section in this
		 manpage   for	more
		 details.

       Translation threshold.
		 The  n	 number	  of
		 times	 a   PA-RISC
		 basic block must be
		 interpreted  before
		 it is considered as
		 a   candidate	 for
		 dynamic    transla‐
		 tion.

		 This  option can be
		 used  to  tune	 the
		 PA-RISC application
		 performance   under
		 ARIES.

		 The  valid range of
		 values	 for  n	  is
		 from to (defined in

		 The  default  value
		 of this option is

       Trace scheduling threshold.
		 The  n	 number	  of
		 times	a translated
		 block must  execute
		 before	 it  is con‐
		 sidered as a candi‐
		 date	for   second
		 pass	 translation
		 with trace schedul‐
		 ing  and  optimiza‐
		 tions.

		 This  option can be
		 used  to  tune	 the
		 PA-RISC application
		 performance   under
		 ARIES.

		 The  valid range of
		 values	 for  n	  is
		 from to (defined in

		 The  default  value
		 of this option is

       NOTE:  For  optimal   perfor‐
       mance,	a   ratio  of  1:2:2
       should be maintained for	 the
       values  of the ARIES options:
       and

   Example:  ARIES Resource Configu‐
       ration File
       To  execute  a 32-bit PA-RISC
       application   through   ARIES
       using 32 MB of stack, you can
       place an file containing	 the
       following line in user's home
       directory  or  in  the	root
       directory.

       Alternatively, if the follow‐
       ing line	 is  specified,	 the
       stack  size  of 32 MB will be
       applied to all 32-bit PA-RISC
       applications  invoked  by the
       user or by all users  depend‐
       ing  on	ARIES  RC file being
       placed in user's home  direc‐
       tory  or	 in  the root direc‐
       tory.

       Sample ARIES resource config‐
       uration	 files	 are   shown
       below.  You can	modify	them
       to suit your requirements.

       An  example of user's private
       ARIES  RC  file,	 located  in
       his/her home directory

       /home/user1/bin/*app	 -ssz 24576 -heap_ssz 32768
       /home/user1/app2*	 -core_format v1 -corepid
       /home/user1/*/app3	 -reset_all -mem_order
       /home/user1/dll/bin/*	 -osinc 256 -issz 1024 -ts 10
       /home/user1/app5		 -pa_os_cpu
       /usr/bin/X11/xterm	 -ssz 24576 -heap_ssz 32768 -ap_heap_ssz 10240
       /usr/local/bin/*		 -sched_trace -osinc 256 -issz 3072 -nomore
       */*			 -corepid

       An  example of an application
       specific	  ARIES	  RC   file,
       placed	 in    application's
       installation directory

       /opt/App/bin/*		 -reset_all -corepid -ssz 32768 -ts 10
       /opt/App/bin/g*		 -reset_all -issz 4096 -heap_ssz 65536
       /opt/App/bin/ab*		 -reset_all -heap_ssz 32768 -ap_heap_ssz 8196
       /opt/App/bin/gcov	 -reset_all -mem_order
       /opt/App/*		 -nomore

       An example of a	system	wide
       global ARIES RC file, located
       in the root directory

       /			 -corepid
       /usr/bin/app1		 -osinc 256 -issz 1024 -ts 10
       /usr/local/bin/*		 -core_format v1
       /opt/App/*/app3		 -mem_order
       /usr/local/*/bin/xv	 -ssz 24576 -heap_ssz 32768 -ap_heap_ssz 5120

ARIES MEMORY MANAGEMENT
   ARIES Managed Area (AMA)
       ARIES consumes a small amount
       of  memory (called ARIES Man‐
       aged AREA (AMA)) towards	 the
       end  of	the PA-RISC applica‐
       tion's private data  segment.
       AMA  is	reserved exclusively
       for   ARIES   use   by	 the
       Integrity   HP-UX   operating
       system.	 The  AMA  size	  is
       decided	by these kernel tun‐
       able parameters:

	      ·	 pa_maxssiz_32bit
		 for 32-bit ARIES

	      ·	 pa_maxssiz_64bit
		 for 64-bit ARIES

       See  pa_maxssiz(5)  for	more
       details.

       The Integrity HP-UX OS passes
       a pointer to a  structure  of
       type  defined  in  to  ARIES.
       The start and end of AMA	 are
       marked  by  and respectively.
       ARIES uses AMA to store	fol‐
       lowing data:

       1.  ARIES's initialized data,
	   un-initialized data (BSS)
	   and	thread local storage
	   (TLS).

       2.  ARIES heap  for  internal
	   calls  and  for  creating
	   ARIES threads for  emula‐
	   tion	 of PA-RISC applica‐
	   tion's threads.

       3.  PA-RISC     application's
	   stack.

       4.  Translated	code  buffer
	   (code cache region).

       5.  Data structures to access
	   and manage the translated
	   code blocks.

       6.  AMAP data structures	 for
	   mapping  of PA-RISC basic
	   blocks   and	  translated
	   code block addresses.

       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 (res‐
       ident memory) as compared  to
       native  PA-RISC	system.	 The
       increase in process  resident
       memory size depends on actual
       memory allocated from AMA.

   Relation	Between	    pa_maxs‐
       siz_32|64bit and ARIES Param‐
       eters
       If the value of	kernel	tun‐
       able   parameter	 maxssiz  is
       much higher than its  default
       value,  any additional memory
       obtained	 by  increasing	 the
       kernel	 tunable   parameter
       pa_maxssiz_32/64bit  will  be
       used by ARIES to increase the
       size of	PA-RISC	 application
       stack  and it may not be pos‐
       sible to increase the size of
       ARIES  parameter	 To  achieve
       optimal memory utilization in
       such   cases,  HP  recommends
       that you limit  the  size  of
       PA-RISC	application stack by
       setting ARIES option value to
       a  reasonable value e.g.	 and
       use ARIES option to  increase
       the  size of ARIES heap to be
       able to create more number of
       threads	than  possible	with
       default ARIES option values.

       At  process   startup   time,
       ARIES   reserves	  space	 for
       PA-RISC	 application   stack
       with  its  maximum  size com‐
       puted as:

	      1.  Current  value  of
		  kernel     tunable
		  parameter maxssiz.

	      2.  Stack	 size  value
		  obtained from par‐
		  ent process.

       Total  size  of	all   memory
       areas  in  AMA should be less
       than or equal to kernel	tun‐
       able    parameter    pa_maxs‐
       siz_32bit  value.    AMA	  is
       divided into different memory
       regions as:

	    pa_maxssiz_32bit = max_pa_stack_size +
			       ARIES heap size (heap_ssz) +
			       ARIES translation code buffer size (ccsz) +
			       ARIES AMAP size (amapsz) +
			       ARIES code cache descriptors size (descsz) +
			       ARIES translator heap (exc_dynt_heap_ssz) +
			       5 MB (ARIES data etc)

       1. If a 32-bit PA-RISC appli‐
	  cation   requires  128  MB
	  stack, set the kernel tun‐
	  able	 parameter  pa_maxs‐
	  siz_32bit to:

	  128  MB  (ssz)  +  22	  MB
	  (heap_ssz)  + 16 MB (ccsz)
	  + 16 MB (amapsz)  +  8  MB
	  (descsz)     +     5	  MB
	  (exc_dynt_heap_ssz) + 5 MB
	  = 200 MB

       2. If a 32-bit PA-RISC appli‐
	  cation requires 128 MB  of
	  ARIES heap, set the kernel
	  tunable parameter pa_maxs‐
	  siz_32bit to:

	  8   MB   (ssz)  +  128  MB
	  (heap_ssz) + 16 MB  (ccsz)
	  +  16	 MB  (amapsz) + 8 MB
	  (descsz)    +	    5	  MB
	  (exc_dynt_heap_ssz) + 5 MB
	  = 186 MB

       64-bit  ARIES  follows	same
       conventions  as	32-bit ARIES
       for managing  AMA.   The	 AMA
       size  is determined by kernel
       tunable	parameter   pa_maxs‐
       siz_64bit    value.    64-bit
       ARIES has 24 MB of fixed mem‐
       ory area (for ARIES data etc)
       compared to 5 MB	 for  32-bit
       ARIES.

EMULATION   OF	PA-RISC	 APPLICATION
       THREADS UNDER ARIES
   Calculation of the Required	Size
       for ARIES Heap
       For   emulation	 of  PA-RISC
       application's threads,  ARIES
       creates	  its	own   native
       threads.	  For  new  threads,
       ARIES  allocates	 memory	 for
       thread specific data,  thread
       stack,	and  thread  backing
       store.  The  memory  require‐
       ment for each thread creation
       in ARIES is as follows:

	      ·	 For 32-bit ARIES

	      ·	 For 64-bit ARIES

       ARIES divides the  heap	area
       into  two  parts.   The first
       part is used  for  the  ARIES
       private	heap  and the second
       part is used  for  allocation
       of new threads.	Thus:

	    Required ARIES Heap Size =
		ap_heap_ssz (KB) + (number of PA-RISC application threads) *
		      (Memory required per ARIES thread, in KB)

   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 ker‐
       nel    tunable	 parameters,
       pa_maxssiz_32bit and pa_maxs‐
       siz_64bit.

       Make  sure  that	 the  kernel
       tunable		   parameter
       max_thread_proc value is suf‐
       ficiently large to create the
       required number of threads.

       Increase	 the  value of ARIES
       option  if  your	 application
       requires	  more	 number	  of
       threads	 than	allowed	  by
       default under ARIES.

       NOTE:  The free memory in AMA
       is not automatically used for
       application  stack  or  ARIES
       heap.	Appropriate    ARIES
       option  must  be specified to
       change the size of particular
       memory area in AMA.

   EMULATION  OF  MxN  THREADS UNDER
       ARIES
       ARIES supports PA-RISC appli‐
       cations which are linked with
       MxN pthreads  library.	From
       HP-UX   11i  Version  2	(and
       above), the PA-RISC  pthreads
       library	    delivered	  on
       Integrity  systems   is	 MxN
       enabled.

       Due to underlying design com‐
       plexities of  true  emulation
       of  MxN	threads under ARIES,
       the correctness and reliabil‐
       ity  may	 need  to be compro‐
       mised.	 Hence	 ARIES	  is
       designed to support emulation
       of  PA-RISC  HP-UX   applica‐
       tions,	 linked	  with	 MxN
       pthreads library,  in  tradi‐
       tional  1x1  mode  by forcing
       environment variable to

       The ARIES policy	 to  emulate
       MxN  threads  as	 traditional
       1x1 thread is not  likely  to
       change  in  current or future
       HP-UX releases.

EMULATION  OF  PA-RISC	 APPLICATION
       STACK UNDER ARIES
       The  stack  allocated  by the
       Integrity  HP-UX	 kernel	  is
       used  by	 ARIES	as  its	 own
       native stack.  Stack for	 the
       PA-RISC applications is allo‐
       cated by ARIES from  the	 AMA
       area.

       Most PA-RISC applications run
       as  expected   with   default
       stack   size  set  by  ARIES.
       However,	 if   your   PA-RISC
       application fails with a core
       dump,  with   the   following
       error   message,	  then	 you
       should increase	the  PA-RISC
       application   stack  size  by
       using  ARIES  option  in	 the
       ARIES RC file.

   How	ARIES  Sets PA-RISC Applica‐
       tion Stack Size
       At  process   startup   time,
       ARIES uses following criteria
       to set the stack size for the
       PA-RISC application.

       1.  ARIES  option value if is
	   specified in the ARIES RC
	   file.

       2.  The	 stack	 size  value
	   inherited from the parent
	   process,   If  the  ARIES
	   option is not present  in
	   the ARIES RC file.

	   In  most cases, the stack
	   size value inherited from
	   the parent process is the
	   current value  of  kernel
	   tunable  parameter  maxs‐
	   siz, or the value in	 the
	   shell.

       For  details  on	 the maximum
       possible	 stack	size   under
       ARIES,  Refer  to the section
       in  this	 manpage  for	more
       details.

       NOTE:   Stack  sizes  can  be
       inherited   among   Integrity
       system	 native	   processes
       (32-bit and 64-bit) and	emu‐
       lated	PA-RISC	   processes
       (32-bit	and  64-bit),	sub‐
       jected  to  the limitation on
       available stack	space  under
       ARIES.

ARIES PERFORMANCE
       For  comparison	purpose, the
       following machine  configura‐
       tions are assumed:

       Model rx4640, Itanium2 4 CPU,
       clock speed 1500 MHz, 6 MB L3
       cache, 8 GB memory

       Model  rp4440,  PA8800  2 CPU
       dual core, clock	 speed	1000
       MHz,  32 MB off chip cache, 8
       GB memory

       The  following  table   shows
       relative	   performance	  of
       PA-RISC	applications   under
       ARIES  on an Integrity system
       at 1500 MHz CPU clock speed.

       ────────────────────────────────────────────────────────
       Application Class	     Compared to   Compared to
				       Integrity	HP9000
					  system	system
       ────────────────────────────────────────────────────────
       General (mix of I/O, memory,	 60-70 %      80-110 %
       system intensive ops)

       Integer intensive		 45-60 %      80-110 %

       Floating point			 20-30 %       40-60 %
       intensive

       Java based			 40-70 %       50-80 %
       applications

       Multi threaded			 50-60 %       70-80 %
       applications

       ────────────────────────────────────────────────────────

       The performance numbers shown
       in   above   table  are	only
       indicative.  The actual	per‐
       formance	  of   your  PA-RISC
       application may vary  depend‐
       ing on the application execu‐
       tion  profile.	You   should
       benchmark   your	 application
       performance  under  ARIES  on
       Integrity    systems   before
       actual deployment.

   The class  of  applications	that
       experience  good	 performance
       under ARIES:
       1.  General     applications,
	   which have average mix of
	   I/O	 intensive,   memory
	   intensive	and   system
	   intensive operations.

       2.  Integer intensive  appli‐
	   cations  which spend sig‐
	   nificant  time  in  algo‐
	   rithmic computations.

       3.  Any	category  of PA-RISC
	   applications	    migrated
	   from	 old PA-RISC systems
	   like N-class and earlier.

       4.  Static  image   rendering
	   graphics applications (no
	   animations).

       5.  Certain  data  base	 and
	   client applications.

   The	class  of  applications that
       experience  poor	 performance
       under ARIES:
       1.  Floating  point intensive
	   applications	 like	most
	   scientific	 simulation,
	   modeling    applications.
	   The	performance slowdown
	   is due  to  architectural
	   differences	     between
	   PA-RISC  and	  Itanium(R)
	   processor   features	 and
	   resources  for   floating
	   point operations.

       2.  Java-based  applications.
	   Unless  your	 application
	   has	  JNI	 code,	 use
	   Integrity   native	JVM.
	   Depending   on  execution
	   profile,  performance  of
	   Java	 applications varies
	   significantly       under
	   ARIES.

       3.  Multi-threaded   applica‐
	   tions that spend signifi‐
	   cant	 amount	 of  time in
	   thread    synchronization
	   operations.	 Thread sus‐
	   pension operation experi‐
	   ences   slow	 performance
	   under ARIES.

       4.  PA-RISC	applications
	   which   use	 performance
	   libraries such as are not
	   good	 candidates  to	 run
	   under ARIES.	 It  is	 not
	   possible   for  ARIES  to
	   emulate   the    detailed
	   behavior  of the applica‐
	   tion for maximum emulated
	   hardware   resource	uti‐
	   lization.

       5.  PA-RISC	applications
	   experience  poor  perfor‐
	   mance under ARIES.	Such
	   applications	 would	exe‐
	   cute with better  perfor‐
	   mance under ARIES if they
	   can use and send graphics
	   data using

       6.  PA-RISC	applications
	   which   frequently	 use
	   variables or are compiled
	   with option

   ARIES Performance Tuning
       Users may find following tips
       useful for tuning the perfor‐
       mance of their PA-RISC appli‐
       cations under ARIES:

       1.  For	 applications  which
	   are very much loop inten‐
	   sive,  reduce  the  ARIES
	   translation	   threshold
	   value (ARIES option

       2.  For applications that run
	   for a long  duration	 and
	   have	  good	locality  of
	   execution (few  functions
	   account  for	 significant
	   portion of  total  execu‐
	   tion	 time), you may con‐
	   sider   enabling    trace
	   scheduling  (ARIES option
	   flag

       3.  If  trace  scheduling  is
	   enabled, you may consider
	   fine	 tuning	 the   trace
	   scheduling	   threshold
	   (ARIES option

       4.  For	long  running	Java
	   applications	  that	have
	   large  methods,  consider
	   increasing  the  size  of
	   ARIES  AMAP	for  dynami‐
	   cally    generated	code
	   (ARIES option

       5.  For	some  rare  applica‐
	   tions   that	 access	 and
	   modify the Floating Point
	   Access  Register  (FPSR :
	   fr0L) register in a loop,
	   consider  enabling trans‐
	   lations for	such  blocks
	   (ARIES option flag

       6.  Some applications experi‐
	   ence good performance  if
	   ARIES  maps	emulated  FP
	   register context on	gen‐
	   eral	  registers.   While
	   others would perform well
	   if  this  optimization is
	   disabled.	    Consider
	   changing the ARIES option
	   flag

       7.  Some	  applications	 may
	   show	 slight	 performance
	   gain	 if  re-ordering  of
	   state  changing  instruc‐
	   tions and memory loads is
	   enabled   (ARIES   option
	   flag

	   WARNING:   Some    multi-
	   threaded	applications
	   like JVM might fail	with
	   core	 dump  if  ARIES re-
	   orders   state   changing
	   PA-RISC instructions.

       8.  Some	  applications	that
	   have large  text  segment
	   size	 or load many shared
	   libraries   may   require
	   large  code	cache region
	   size	 (ARIES	 option	 For
	   best	 results  make	sure
	   that	  sizes	  of   these
	   parameters	are  in	 the
	   ratio 1:2:2.

       9.  Some	 applications	that
	   require  ARIES  to  spend
	   significant	  time	  in
	   dynamic  translations may
	   work faster	if  transla‐
	   tions  are  cached (ARIES
	   option The save and	load
	   of  translated code works
	   best	   for	  statically
	   linked applications.

	   WARNING:   Some   PA-RISC
	   applications may not work
	   correctly  with the load‐
	   ing	of   ARIES   dynamic
	   translations	  cached  on
	   disk during previous exe‐
	   cutions   of	  the	same
	   application.

ARIES SUPPORTED APPLICATIONS
       ·  ARIES	 supports  emulation
	  of all well-behaved (those
	  applications that  do	 not
	  use	un-documented	fea‐
	  tures)    PA-RISC    HP-UX
	  applications	and that run
	  fine on latest HP-UX	ver‐
	  sion on PA-RISC systems.

       ·  ARIES	 supports  all HP-UX
	  Inter-Process	  Communica‐
	  tion	mechanisms  such  as
	  semaphores, pipes,  shared
	  memory,    and    sockets,
	  between  Integrity  native
	  and  emulated PA-RISC pro‐
	  cesses.

       ·  The exact signal/exception
	  behavior  of PA-RISC HP-UX
	  applications, is supported
	  under ARIES.

       ·  There is only a very small
	  subset  of   the   PA-RISC
	  application	domain	that
	  are  not  supported  under
	  ARIES.

       ·  To   ascertain  whether  a
	  particular	 application
	  will	run  correctly under
	  ARIES or not, determine if
	  the application falls into
	  one of the  ARIES  limita‐
	  tions	  described  in	 the
	  section in this manpage.

ARIES LIMITATIONS
       ARIES supports  emulation  of
       all  PA-RISC  HP-UX  applica‐
       tions,  with  the   following
       limitations   and/or   excep‐
       tions:

       1.  ARIES  does	not  support
	   PA-RISC applications that
	   load	  Integrity   native
	   shared  libraries.  ARIES
	   is meant  only  for	pure
	   PA-RISC   HP-UX  applica‐
	   tions  that	are   either
	   statically or dynamically
	   linked    with    PA-RISC
	   libraries only.

       2.  The	version	 of ARIES at
	   this	  release   supports
	   PA-RISC   HP-UX  applica‐
	   tions that  run  fine  on
	   contemporary	       HP-UX
	   release version on native
	   PA-RISC systems.

       3.  ARIES  does	not  support
	   privileged	     PA-RISC
	   instructions.      Hence,
	   device drivers and  load‐
	   able	 kernel	 modules are
	   not supported.

       4.  ARIES does not  guarantee
	   correct    emulation	  of
	   PA-RISC	applications
	   which   make	 assumptions
	   about "time taken to exe‐
	   cute	  certain  parts  of
	   application	code  and/or
	   system    calls".	Such
	   applications are theoret‐
	   ically   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 or
	   system  calls.   However,
	   ARIES  supports debugging
	   of emulated	applications
	   using  PA-RISC  Refer  to
	   the section in this	man‐
	   page	 for  more  informa‐
	   tion.

       6.  ARIES  consumes  a  small
	   amount of memory from the
	   emulated    application's
	   virtual   memory  address
	   space.   Therefore  ARIES
	   does not support applica‐
	   tions that are nearly  or
	   completely  maxed  out on
	   their   virtual   address
	   space  usage in data seg‐
	   ment.

       7.  ARIES  does	not  support
	   applications that rely on
	   differences	between	 and
	   system  calls.   However,
	   most	 applications	that
	   use	the  system  call do
	   use	it  with  a  purpose
	   which  is  well  known to
	   the programmer.  It is an
	   extremely  rare condition
	   that a standard  applica‐
	   tion	 would have any such
	   reliance on	the  differ‐
	   ences  between and system
	   calls.  See vfork(2)	 and
	   fork(2) for details.

       8.  ARIES returns information
	   pertinent  to  a  PA-RISC
	   2.0	processor,  for cer‐
	   tain system	calls.	 For
	   instance,  a call made to
	   with will return  If	 the
	   application requires that
	   it be able  to  determine
	   that	 it is running on an
	   Integrity system, then it
	   should  use	the call and
	   the Integrity native com‐
	   mand	 to get the required
	   fields.  See	 sysconf(2),
	   system(3S),	  and	get‐
	   conf(1) for more informa‐
	   tion.

AUTHOR
       ARIES was developed by HP.

SEE ALSO
       file(1),	 gdb(1), getconf(1),
       init(1M),	 coreadm(2),
       execve(2),    fork(2),	get‐
       pid(2),	getrlimit(2),  setr‐
       limit(2),	  signal(2),
       sysconf(2),	  ulimit(2),
       uname(2),    vfork(2),	sys‐
       tem(3S), core(4), maxssiz(5),
       pa_maxssiz(5).

			   HP Integrity Systems Only		      ARIES(5)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net