doc: Adjust doxyfile and rst file based on multi-arch change

Some inputs and references need to change accordingly.

Tracked-On: #8830
Signed-off-by: Yifan Liu <yifan1.liu@intel.com>
This commit is contained in:
Yifan Liu
2025-10-28 06:23:27 +00:00
committed by acrnsi-robot
parent 0e333ca422
commit 8d7aaf67f8
2 changed files with 6 additions and 4 deletions

View File

@@ -796,7 +796,6 @@ WARN_LOGFILE =
INPUT = custom-doxygen/mainpage.md \
../hypervisor/arch/x86/guest/trusty.c \
../hypervisor/include/arch/x86/asm/guest/guest_memory.h \
../hypervisor/include/arch/x86/asm/guest/ept.h \
../hypervisor/include/arch/x86/asm/mmu.h \
../hypervisor/include/arch/x86/asm/cpu.h \
@@ -824,6 +823,9 @@ INPUT = custom-doxygen/mainpage.md \
../hypervisor/include/common/timer.h \
../hypervisor/include/common/ptdev.h \
../hypervisor/include/common/pgtable.h \
../hypervisor/include/common/vcpu.h \
../hypervisor/include/common/vm.h \
../hypervisor/include/common/guest_memory.h \
../hypervisor/include/public/acrn_common.h \
../hypervisor/include/public/acrn_hv_defs.h \
../devicemodel/include/virtio.h \

View File

@@ -121,7 +121,7 @@ a subset of it.
The ACRN hypervisor does not support virtual CPU migration to
different physical CPUs. No changes to the mapping of the virtual CPU to
physical CPU can happen without first calling ``offline_vcpu``.
physical CPU can happen without first calling ``destroy_vcpu``.
.. _vCPU_lifecycle:
@@ -164,7 +164,7 @@ lifecycle:
.. doxygenfunction:: reset_vcpu
:project: Project ACRN
.. doxygenfunction:: offline_vcpu
.. doxygenfunction:: destroy_vcpu
:project: Project ACRN
@@ -213,7 +213,7 @@ Some example scenario flows are shown here:
- **During VM shutdown**: *pause_vm* function forces a vCPU
running in *vcpu_thread* to schedule out to *default_idle*. The
following *reset_vcpu* and *offline_vcpu* de-init and then offline
following *reset_vcpu* and *destroy_vcpu* de-init and then offline
this vCPU instance.
- **During IOReq handling**: after an IOReq is sent to DM for emulation, a