mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-09-24 02:08:04 +00:00
doc: fix misspellings
Fix misspellings missed during regular reviews Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
committed by
David Kinder
parent
a29ef9178e
commit
1e8269b5f7
@@ -318,7 +318,7 @@ Step 3: Deploy the Service VM image
|
||||
The operation has completed successfully.
|
||||
|
||||
#. Follow these steps to create two partitions on the U disk.
|
||||
Keep 4GB in the first partition and leave free space in the second parition.
|
||||
Keep 4GB in the first partition and leave free space in the second partition.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
@@ -92,7 +92,7 @@ The procedure for enabling S5 is specific to the particular OS:
|
||||
|
||||
.. note:: For RT-Linux, the vUART is emulated in the hypervisor; expose the node as ``/dev/ttySn``.
|
||||
|
||||
#. For LaaG and RT-Linux VMs, run the life-cycle manager deamon:
|
||||
#. For LaaG and RT-Linux VMs, run the life-cycle manager daemon:
|
||||
|
||||
a. Use these commands to build the life-cycle manager daemon, ``life_mngr``.
|
||||
|
||||
@@ -116,7 +116,7 @@ The procedure for enabling S5 is specific to the particular OS:
|
||||
# systemctl enable life_mngr.service
|
||||
# reboot
|
||||
|
||||
#. For the WaaG VM, run the life-cycle manager deamon:
|
||||
#. For the WaaG VM, run the life-cycle manager daemon:
|
||||
|
||||
a) Build the ``life_mngr_win.exe`` application::
|
||||
|
||||
|
@@ -12,7 +12,7 @@ higher priorities VMs (such as RTVMs) are not impacted.
|
||||
|
||||
Using RDT includes three steps:
|
||||
|
||||
1. Detect and enumerate RDT allocation capabilites on supported resources such as cache and memory bandwidth.
|
||||
1. Detect and enumerate RDT allocation capabilities on supported resources such as cache and memory bandwidth.
|
||||
#. Set up resource mask array MSRs (Model-Specific Registers) for each CLOS (Class of Service, which is a resource allocation), basically to limit or allow access to resource usage.
|
||||
#. Select the CLOS for the CPU associated with the VM that will apply the resource mask on the CP.
|
||||
|
||||
@@ -28,8 +28,8 @@ For further details, refer to the ACRN RDT high-level design :ref:`hv_rdt` and `
|
||||
|
||||
.. _rdt_detection_capabilities:
|
||||
|
||||
RDT detection and resource capabilites
|
||||
**************************************
|
||||
RDT detection and resource capabilities
|
||||
***************************************
|
||||
From the ACRN HV debug shell, use ``cpuid`` to detect and identify the
|
||||
resource capabilities. Use the platform's serial port for the HV shell
|
||||
(refer to :ref:`getting-started-up2` for setup instructions).
|
||||
@@ -38,7 +38,7 @@ Check if the platform supports RDT with ``cpuid``. First, run ``cpuid 0x7 0x0``;
|
||||
RDT. Next, run ``cpuid 0x10 0x0`` and check the EBX [3-1] bits. EBX [bit 1]
|
||||
indicates that L3 CAT is supported. EBX [bit 2] indicates that L2 CAT is
|
||||
supported. EBX [bit 3] indicates that MBA is supported. To query the
|
||||
capabilties of the supported resources, use the bit position as a subleaf
|
||||
capabilities of the supported resources, use the bit position as a subleaf
|
||||
index. For example, run ``cpuid 0x10 0x2`` to query the L2 CAT capability.
|
||||
|
||||
.. code-block:: none
|
||||
@@ -149,7 +149,7 @@ Configure RDT for VM using VM Configuration
|
||||
.. note::
|
||||
Users can change the mask values, but the cache mask must have **continuous bits** or a #GP fault can be triggered. Similary, when programming an MBA delay value, be sure to set the value to less than or equal to the MAX delay value.
|
||||
|
||||
#. Set up the CLOS in the VM config. Follow `RDT detection and resource capabilites`_ to identify the MAX CLOS that can be used. ACRN uses the **the lowest common MAX CLOS** value among all RDT resources to avoid resource misconfigurations. For example, configuration data for the Service VM sharing mode can be found at ``hypervisor/arch/x86/configs/vm_config.c``
|
||||
#. Set up the CLOS in the VM config. Follow `RDT detection and resource capabilities`_ to identify the MAX CLOS that can be used. ACRN uses the **the lowest common MAX CLOS** value among all RDT resources to avoid resource misconfigurations. For example, configuration data for the Service VM sharing mode can be found at ``hypervisor/arch/x86/configs/vm_config.c``
|
||||
|
||||
.. code-block:: none
|
||||
:emphasize-lines: 6
|
||||
|
@@ -6,7 +6,7 @@ Real-Time (RT) Performance Analysis on ACRN
|
||||
The document describes the methods to collect trace/data for ACRN Real-Time VM (RTVM)
|
||||
real-time performance analysis. Two parts are included:
|
||||
|
||||
- Method to trace ``vmexit`` occurences for analysis.
|
||||
- Method to trace ``vmexit`` occurrences for analysis.
|
||||
- Method to collect Performance Monitoring Counters information for tuning based on Performance Monitoring Unit, or PMU.
|
||||
|
||||
``vmexit`` analysis for ACRN RT performance
|
||||
@@ -65,7 +65,7 @@ Offline analysis
|
||||
|
||||
#. Convert the raw trace data to human readable format.
|
||||
#. Merge the logs in the RTVM and the ACRN hypervisor trace based on timestamps (in TSC).
|
||||
#. Check to see if any ``vmexit`` occured within the critical sections. The pattern is as follows:
|
||||
#. Check to see if any ``vmexit`` occurred within the critical sections. The pattern is as follows:
|
||||
|
||||
.. figure:: images/vm_exits_log.png
|
||||
:align: center
|
||||
|
@@ -185,7 +185,7 @@ Re-use and modify the `launch_win.sh` script in order to launch the new Debian 1
|
||||
$ sudo cp /mnt/EFI/debian/grubx64.efi /mnt/EFI/boot/bootx64.efi
|
||||
$ sync && sudo umount /mnt
|
||||
|
||||
#. Launch the Debian VM afer logging in to the Service VM:
|
||||
#. Launch the Debian VM after logging in to the Service VM:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
@@ -63,9 +63,9 @@ Validated Versions
|
||||
Build the Ubuntu KVM Image
|
||||
**************************
|
||||
|
||||
This tutorial uses the Ubuntu 18.04 destop ISO as the base image.
|
||||
This tutorial uses the Ubuntu 18.04 desktop ISO as the base image.
|
||||
|
||||
#. Download the `Ubuntu 18.04 destop ISO <http://releases.ubuntu.com/18.04.3/ubuntu-18.04.3-desktop-amd64.iso?_ga=2.160010942.221344839.1566963570-491064742.1554370503>`_ on your development machine:
|
||||
#. Download the `Ubuntu 18.04 desktop ISO <http://releases.ubuntu.com/18.04.3/ubuntu-18.04.3-desktop-amd64.iso?_ga=2.160010942.221344839.1566963570-491064742.1554370503>`_ on your development machine:
|
||||
|
||||
#. Install Ubuntu via the virt-manager tool:
|
||||
|
||||
@@ -165,7 +165,7 @@ Modify the `launch_win.sh` script in order to launch Ubuntu as the User VM.
|
||||
$ sed -i 3"s/$/ i915.enable_conformance_check=0/" /mnt/loader/entries/acrn.conf
|
||||
$ sudo sync && sudo umount /mnt && reboot
|
||||
|
||||
#. Launch the Ubuntu VM afer logging in to the Service VM:
|
||||
#. Launch the Ubuntu VM after logging in to the Service VM:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
@@ -35,4 +35,4 @@ Steps to sign the binaries of the Clear Linux image
|
||||
|
||||
$ sudo sh sign_image.sh $PATH_TO_CLEAR_IMAGE $PATH_TO_KEY $PATH_TO_CERT
|
||||
|
||||
#. **clear-xxx-kvm.img.signed** will be generated in the same folder as the original clear-xxx-kvm.img.
|
||||
#. **clear-xxx-kvm.img.signed** will be generated in the same folder as the original clear-xxx-kvm.img.
|
||||
|
@@ -89,4 +89,4 @@ Hybrid Scenario Startup Checking
|
||||
#. Use the ``vm_console 2`` command to switch to the VM2 (User VM) console.
|
||||
#. Verify that VM2 can boot up and you can log in.
|
||||
|
||||
Refer to the :ref:`acrnshell` for more information about available commands.
|
||||
Refer to the :ref:`acrnshell` for more information about available commands.
|
||||
|
@@ -158,7 +158,7 @@ the network:
|
||||
GVT-g feature for that VM. Refer the :ref:`APL_GVT-g-hld` for
|
||||
detailed information.
|
||||
|
||||
Here's a screen shot of the resuting launch of the Clear Linux and Ubuntu
|
||||
Here's a screen shot of the resulting launch of the Clear Linux and Ubuntu
|
||||
User VMs, with a Clear Linux Service VM:
|
||||
|
||||
.. figure:: images/sdc2-launch-2-laag.png
|
||||
|
@@ -12,9 +12,9 @@ This tutorial describes how to run Xenomai as the User VM OS (Real-Time VM) on t
|
||||
Build the Xenomai kernel
|
||||
************************
|
||||
|
||||
Follow these instructions to buid the Xenomai kernel:
|
||||
Follow these instructions to build the Xenomai kernel:
|
||||
|
||||
#. Clone the Xenomai kernel souce code::
|
||||
#. Clone the Xenomai kernel source code::
|
||||
|
||||
$ git clone -b F/4.19.59/base/ipipe/xenomai_3.1 https://github.com/intel/linux-stable-xenomai
|
||||
|
||||
|
Reference in New Issue
Block a user