1 s-Par Proc Entries 2This document describes the proc entries created by the Unisys s-Par modules. 3 4Support Module Entries 5These entries are provided primarily for debugging. 6 7/proc/uislib/info: This entry contains debugging information for the 8uislib module, including bus information and memory usage. 9 10/proc/visorchipset/controlvm: This directory contains debugging 11entries for the controlvm channel used by visorchipset. 12 13/proc/uislib/platform: This entry is used to display the platform 14number this node is in the system. For some guests, this may be 15invalid. 16 17/proc/visorchipset/chipsetready: This entry is written to by scripts 18to signify that any user level activity has been completed before the 19guest can be considered running and is shown as running in the s-Par 20UI. 21 22Device Entries 23These entries provide status of the devices shared by a service partition. 24 25/proc/uislib/vbus: this is a directory containing entries for each 26virtual bus. Each numbered sub-directory contains an info entry, which 27describes the devices that appear on that bus. 28 29/proc/uislib/cycles_before_wait: This entry is used to tune 30performance, by setting the number of cycles we wait before going idle 31when in polling mode. A longer time will reduce message latency but 32spend more processing time polling. 33 34/proc/uislib/smart_wakeup: This entry is used to tune performance, by 35enabling or disabling smart wakeup. 36 37/proc/virthba/info: This entry contains debugging information for the 38virthba module, including interrupt information and memory usage. 39 40/proc/virthba/enable_ints: This entry controls interrupt use by the 41virthba module. Writing a 0 to this entry will disable interrupts. 42 43/proc/virtnic/info: This entry contains debugging information for the 44virtnic module, including interrupt information, send and receive 45counts, and other device information. 46 47/proc/virtnic/ethX: This is a directory containing entries for each 48virtual NIC. Each named subdirectory contains two entries, 49clientstring and zone. 50 51/proc/virtpci/info: This entry contains debugging information for the 52virtpci module, including virtual PCI bus information and device 53locations. 54 55/proc/virtnic/enable_ints: This entry controls interrupt use by the 56virtnic module. Writing a 0 to this entry will disable interrupts. 57 58Visorconinclient, visordiag, visornoop, visorserialclient, and 59visorvideoclient Entries 60 61The entries in proc for these modules all follow the same 62pattern. Each module has its own proc directory with the same name, 63e.g. visordiag presents a /proc/visordiag directory. Inside of the 64module's directory are a device directory, which contains one numbered 65directory for each device provided by that module. Each device has a 66diag entry that presents the device number and visorbus name for that 67device. The module directory also has a driver/diag entry, which 68reports the corresponding s-Par version number of the driver. 69 70Automated Installation Entries 71 72These entries are used to pass information between the s-Par platform 73and the Linux-based installation and recovery tool. These values are 74read/write, however, the guest can only reset them to 0, or report an 75error status through the installer entry. The values are only set via 76s-Par's firmware interface, to help prevent accidentally booting into 77the tool. 78 79/proc/visorchipset/boottotool: This entry instructs s-Par that the 80next reboot will launch the installation and recovery tool. If set to 810, the next boot will happen according to the UEFI boot manager 82settings. 83 84/proc/visorchipset/toolaction: This entry indicates the installation 85and recovery tool mode requested for the next boot. 86 87/proc/visorchipset/installer: this entry is used by the installation 88and recovery tool to pass status and result information back to the 89s-Par firmware. 90 91/proc/visorchipset/partition: This directory contains the guest 92partition configuration data for each virtual bus, for use during 93installation and at runtime for s-Par service partitions. 94