Download XtratuM User Manual - ESA Microelectronics Section

31/134
2.14. Access to devices
Bits 7..0 (partitionId): The Id attribute of the partition that caused the event.
seq: Number of sequence enabling to sort the event respect other events. It is codified as unsigned
805
integer, incremented each time a new HM event is logged.
timeStamp: A time stamp of when the event was detected.
Either cpuCtxt or payload: When validCpuCtxt bit is set (opCode), then this field holds the processor context when the HM event was generated, otherwise, this field may hold information of the
generated event. For instance, an application can manually generate a HM event specifying this
information.
2.13.5
810
Multicore implications
Health monitor management has not visibility on the VCPUs internal to the partitions. From this point
of view, a trap generated by a VCPU will:
• will raise a HM event
815
• XtratuM will handle the event as execute the action defined in the configuration file which is
common to all the internal VCPUs.
• In the case of a propagation action, XtratuM identifies the VCPU that generated the trap and
delivers to the causing VCPU the associated virtual interrupt
• In the case of a partition action (halt, reset, etc.), the action is aplied independently of the causing
VCPU.
2.14
820
Access to devices
Partition
Partition
XM_sparcv8_HWoutport()
XM_sparcv8_HWinport()
Partition
Sampling or queuing ports
XM_sparcv8_HWoutport()
XM_sparcv8_HWinport()
XtratuM
Device registers
Device
(a) Partition using exclusively a device.
Partition
XtratuM
Device registers
Device
(b) I/O Server partition.
A partition, using exclusively a device (peripheral), can access the device through the device driver
implemented in the partition (figure 2.15a). The partition is in charge of handling properly the device.
The configuration file has to specify the I/O ports and the interrupt lines that will be used by each
partition.
825
Two partitions cannot use the same interrupt line. XtratuM provides a fine grain access control to I/O
ports, so that, several partitions can use (read and write) different bits of the the same I/O port. Also,
it is possible to define a range of valid values that can be written in an I/O port (see section 5.10).
When a device is used by several partitions, an user implemented I/O server partition (figure 2.15b)
may be in charge of the device management. An I/O server partition is a specific partition which
xm-4-usermanual-047d
Printed: November 26, 2012
830