Starting and stopping smmuman

#Bootstrap file
[image=0x2000000]
[virtual=x86_64,kpi +compress] boot = {
startup-intel-MX86 -D8250_mmio.0xFC000000^2.115200 -Q enable -v 
[+keeplinked] \
    PATH=/sbin:/bin:/usr/sbin:/usr/bin:/opt/sbin:/opt/bin:/proc/boot \
    LD_LIBRARY_PATH=/lib:/usr/lib:/lib/dll:/lib/dll/pci:/proc/boot procnto-smp-instr
}

[+script] startup-script = {
    display_msg Welcome to the QNX OS on my x86_64 board.

... 

#Concatenate above, the BSP build file of your choosing
[+script] myx86-startup-script = {
    ...
    #Start smmuman and point it to the configuration file.
    smmuman @/etc/myx86.smmu
}

#My board binaries
[perms=0444] /root/envset.sh {
export PCI_HW_MODULE=/lib/dll/pci/pci_hw-Intel_x86_MX86.so
}
...

#Include smmuman configuration file in build.
/etc/myx86.smmu = ${MY_TARGET}/etc/myx86.smmu
...

#Include smmuman in build.
/bin/smmuman = smmuman
/lib/dll/smmu-vtd.so = smmu-vtd.so

• If it finds this device, the service knows that it is running in a guest in a VM and proceeds with its startup.
• If it doesn’t find this device, the service assumes that it is running in the host, and attempts to load the smmu-*.so support library specified by the smmu option in its configuration before proceeding with its startup.

1. The smmuman service doesn’t load a support library, but communicates directly with the IOMMU/SMMU virtual device (vdev-smmu).

   If it doesn’t find a vdev-smmu in its hosting VM (qvm process instance), the smmuman service in the guest reports that the required hardware isn't present and moves to its DSS.

2. When it parses its configuration information, the smmuman service ignores any reserved, smmu, unit, or use options it finds in its configuration, because these options are relevant only to the corresponding smmuman service running in the hypervisor host.
3. The smmuman service queries the vdev-smmu device, which confirms that a smmuman service is running in the hypervisor host and that the hosting VM is attached as a client of the host-level smmuman service. The device also provides the safety-certification status of all the components on which the guest's smmuman service relies:

   • the host-level microkernel and process manager (procnto*)
   • the host-level SMMUMAN components (smmuman, libsmmu.a, and the smmu-*.so support library)
   • the QNX hypervisor components (qvm and the vdev-*.so virtual devices)
     Note:

     The vdev-smmu.so virtual device shared object is a QNX hypervisor component. For more information about this device and how to use it, see the QNX Hypervisor User's Guide.