github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-08-02 08:19:16 +00:00
Code Issues Projects Releases Wiki Activity

doc: update cpu affinity related docs

Browse Source 
Signed-off-by: Zide Chen <zide.chen@intel.com>
This commit is contained in:
Zide Chen 2020-05-07 11:06:49 -07:00 committed by deb-intel
parent c271fc022a
commit 87adc93c96
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/developer-guides/hld/hv-cpu-virt.rst
View File

@ -56,9 +56,9 @@ ACRN then forces a fixed 1:1 mapping between a VCPU and this physical CPU
when creating a VCPU for the guest Operating System. This makes the VCPU
management code much simpler.
``cpu_affinity_bitmap`` in ``vm config`` helps to decide which physical CPU a
``cpu_affinity`` in ``vm config`` helps to decide which physical CPU a
VCPU in a VM affines to, then finalize the fixed mapping. When launching an
user VM, need to choose pCPUs from the VM's cpu_affinity_bitmap that are not
user VM, need to choose pCPUs from the VM's cpu_affinity that are not
used by any other VMs.
Flexible CPU Sharing
@ -67,9 +67,9 @@ Flexible CPU Sharing
To enable CPU sharing, ACRN hypervisor could configure IORR
(IO sensitive Round-Robin) or BVT (Borrowed Virtual Time) scheduler policy.
``cpu_affinity_bitmap`` in ``vm config`` helps to decide which physical CPU two
or more vCPUs from different VMs are sharing. A pCPU can be shared among Service OS
and any user VMs as long as local APIC passthrough is not enabled in that user VM.
``cpu_affinity`` in ``vm config`` indicates all the physical CPUs this VM
is allowed to run on. A pCPU can be shared among Service OS and any user VMs
as long as local APIC passthrough is not enabled in that user VM.
see :ref:`cpu_sharing` for more information.
@ -106,15 +106,15 @@ CPUs intended for UOS use.
CPU management in UOS
=====================
``cpu_affinity_bitmap`` in ``vm config`` defines a set of pCPUs that an User VM
``cpu_affinity`` in ``vm config`` defines a set of pCPUs that an User VM
is allowed to run on. acrn-dm could choose to launch on only a subset of the pCPUs
or on all pCPUs listed in cpu_affinity_bitmap, but it can't assign
or on all pCPUs listed in cpu_affinity, but it can't assign
any pCPU that is not included in it.
CPU assignment management in HV
===============================
The physical CPU assignment is pre-defined by ``cpu_affinity_bitmap`` in
The physical CPU assignment is pre-defined by ``cpu_affinity`` in
``vm config``, while post-launched VMs could be launched on pCPUs that are
a subset of it.

4
doc/tutorials/cpu_sharing.rst
View File

@ -155,10 +155,10 @@ The default scheduler is **SCHED_BVT**.
* The cpu_affinity could be configured by one of these approaches:
- Without ``cpu_affinity`` option in acrn-dm. This launches the user VM
on all the pCPUs that are included in the statically configured cpu_affinity_bitmap.
on all the pCPUs that are included in the statically configured cpu_affinity.
- With ``cpu_affinity`` option in acrn-dm. This launches the user VM on
a subset of the configured cpu_affinity_bitmap pCPUs.
a subset of the configured cpu_affinity pCPUs.
For example, assign physical CPUs 0 and 1 to this VM::