From 9c1c6b80a5ecc875b36346bf431ad8c7904bbdf8 Mon Sep 17 00:00:00 2001 From: "David B. Kinder" Date: Tue, 21 Sep 2021 10:49:08 -0700 Subject: [PATCH] doc: finish renaming vmh to hsm Fixed some additional doc references missed in PR #6283 Signed-off-by: David B. Kinder --- doc/developer-guides/VBSK-analysis.rst | 6 +++--- doc/developer-guides/hld/hld-APL_GVT-g.rst | 4 ++-- doc/developer-guides/hld/virtio-net.rst | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/developer-guides/VBSK-analysis.rst b/doc/developer-guides/VBSK-analysis.rst index 4caec3812..f01bc2d6e 100644 --- a/doc/developer-guides/VBSK-analysis.rst +++ b/doc/developer-guides/VBSK-analysis.rst @@ -80,14 +80,14 @@ two parts: kick overhead and notify overhead. - **Kick Overhead**: The User VM gets trapped when it executes sensitive instructions that notify the hypervisor first. The notification is assembled into an IOREQ, saved in a shared IO page, and then - forwarded to the VHM module by the hypervisor. The VHM notifies its + forwarded to the HSM module by the hypervisor. The HSM notifies its client for this IOREQ, in this case, the client is the vbs-echo backend driver. Kick overhead is defined as the interval from the beginning of User VM trap to a specific VBS-K driver, e.g. when virtio-echo gets notified. - **Notify Overhead**: After the data in virtqueue being processed by the - backend driver, vbs-echo calls the VHM module to inject an interrupt - into the frontend. The VHM then uses the hypercall provided by the + backend driver, vbs-echo calls the HSM module to inject an interrupt + into the frontend. The HSM then uses the hypercall provided by the hypervisor, which causes a User VM VMEXIT. The hypervisor finally injects an interrupt into the vLAPIC of the User VM and resumes it. The User VM therefore receives the interrupt notification. Notify overhead is diff --git a/doc/developer-guides/hld/hld-APL_GVT-g.rst b/doc/developer-guides/hld/hld-APL_GVT-g.rst index c7dbf41ac..c752e70fb 100644 --- a/doc/developer-guides/hld/hld-APL_GVT-g.rst +++ b/doc/developer-guides/hld/hld-APL_GVT-g.rst @@ -923,14 +923,14 @@ AcrnGT in Kernel ================= The AcrnGT module in the Service VM kernel acts as an adaption layer to connect -between GVT-g in the i915, the VHM module, and the ACRN-DM user space +between GVT-g in the i915, the HSM module, and the ACRN-DM user space application: - AcrnGT module implements the MPT interface of GVT-g to provide services to it, including set and unset trap areas, set and unset write-protection pages, etc. -- It calls the VHM APIs provided by the ACRN VHM module in the Service VM +- It calls the HSM APIs provided by the ACRN HSM module in the Service VM kernel, to eventually call into the routines provided by ACRN hypervisor through hyper-calls. diff --git a/doc/developer-guides/hld/virtio-net.rst b/doc/developer-guides/hld/virtio-net.rst index 265fb68c6..c4d3428b7 100644 --- a/doc/developer-guides/hld/virtio-net.rst +++ b/doc/developer-guides/hld/virtio-net.rst @@ -193,7 +193,7 @@ example, showing the flow through each layer: .. code-block:: c - vhm_intr_handler --> // HSM interrupt handler + hsm_intr_handler --> // HSM interrupt handler tasklet_schedule --> io_req_tasklet --> acrn_ioreq_distribute_request --> // ioreq can't be processed in HSM, forward it to device DM @@ -348,7 +348,7 @@ cases.) .. code-block:: c - vhm_dev_ioctl --> // process the IOCTL and call hypercall to inject interrupt + hsm_dev_ioctl --> // process the IOCTL and call hypercall to inject interrupt hcall_inject_msi --> **ACRN Hypervisor**