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

doc: fix misspelling

Browse Source 
Fix misspellings in docs missed during regular reviews

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2020-06-12 16:08:49 -07:00 committed by David Kinder
parent 315b7f3c00
commit 0ad80d1f09
3 changed files with 26 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/introduction/index.rst
View File

@ -198,7 +198,7 @@ Industrial usage scenario:
- a Service VM such as Ubuntu*,
- a Human Machine Interface (HMI) application OS such as Windows*,
- an Artifical Intelligence (AI) application on Linux*,
- an Artificial Intelligence (AI) application on Linux*,
- a Kata Container application, and
- a real-time control OS such as Zephyr*, VxWorks* or RT-Linux*.

2
doc/tutorials/acrn_on_qemu.rst
View File

@ -30,7 +30,7 @@ Pre-Requisites
INFO: /dev/kvm exists
KVM acceleration can be used
2. Ensure the Ubuntu18.04 Host kernel version is **atleast 5.3.0** and above.
2. Ensure the Ubuntu18.04 Host kernel version is **at least 5.3.0** and above.
3. Make sure KVM and the following utilities are installed.

36
doc/tutorials/gpu-passthru.rst
View File

@ -13,9 +13,11 @@ Introduction
************
Intel GVT-d is a graphics virtualization approach that is also known as
the Intel-Graphics-Device passthrough feature. Based on Intel VT-d technology, it offers useful special graphics-related configurations.
It allows for direct assignment of an entire GPU’s prowess to a single user,
passing the native driver capabilities through to the hypervisor without any limitations.
the Intel-Graphics-Device passthrough feature. Based on Intel VT-d
technology, it offers useful special graphics-related configurations.
It allows for direct assignment of an entire GPU's prowess to a single
user, passing the native driver capabilities through to the hypervisor
without any limitations.
Verified version
*****************
@ -44,18 +46,25 @@ BIOS settings
Kaby Lake platform
==================
* Set **IGD Minimum Memory** to **64MB** in **Devices** → **Video** → **IGD Minimum Memory**.
* Set **IGD Minimum Memory** to **64MB** in **Devices** &rarr;
**Video** &rarr; **IGD Minimum Memory**.
Whiskey Lake platform
=====================
* Set **PM Support** to **Enabled** in **Chipset** → **System Agent (SA) Configuration** → **Graphics Configuration** → **PM support**.
* Set **DVMT Pre-Allocated** to **64MB** in **Chipset** → **System Agent (SA) Configuration** → **Graphics Configuration** → **DVMT Pre-Allocated**.
* Set **PM Support** to **Enabled** in **Chipset** &rarr; **System
Agent (SA) Configuration** &rarr; **Graphics Configuration** &rarr;
**PM support**.
* Set **DVMT Pre-Allocated** to **64MB** in **Chipset** &rarr;
**System Agent (SA) Configuration**
&rarr; **Graphics Configuration** &rarr; **DVMT Pre-Allocated**.
Elkhart Lake platform
=====================
* Set **DMVT Pre-Allocated** to **64MB** in **Intel Advanced Menu** → **System Agent(SA) Configuration** → **Graphics Configuration** → **DMVT Pre-Allocated**.
* Set **DMVT Pre-Allocated** to **64MB** in **Intel Advanced Menu**
&rarr; **System Agent(SA) Configuration** &rarr;
**Graphics Configuration** &rarr; **DMVT Pre-Allocated**.
Passthrough the GPU to Guest
****************************
@ -90,8 +99,11 @@ Passthrough the GPU to Guest
Enable the GVT-d GOP driver
***************************
When enabling GVT-d, the Guest OS cannot light up the physical screen before
the OS driver loads. As a result, the Guest BIOS and the Grub UI is not visible on the physical screen. The occurs because the physical display is initialized by the GOP driver or VBIOS before the OS driver loads, and the Guest BIOS doesn’t have them.
When enabling GVT-d, the Guest OS cannot light up the physical screen
before the OS driver loads. As a result, the Guest BIOS and the Grub UI
is not visible on the physical screen. The occurs because the physical
display is initialized by the GOP driver or VBIOS before the OS driver
loads, and the Guest BIOS doesn't have them.
The solution is to integrate the GOP driver binary into the OVMF as a DXE
driver. Then the Guest OVMF can see the GOP driver and run it in the graphic
@ -109,7 +121,8 @@ Steps
#. Fetch the vbt and gop drivers.
Fetch the **vbt** and **gop** drivers from the board manufacturer according to your CPU model name.
Fetch the **vbt** and **gop** drivers from the board manufacturer
according to your CPU model name.
#. Add the **vbt** and **gop** drivers to the OVMF:
@ -154,5 +167,4 @@ Keep in mind the following:
- This will generate the binary at
``Build/OvmfX64/DEBUG_GCC5/FV/OVMF.fd``. Transfer the binary to
your target machine.
- Modify the launch script to specify the OVMF you built just now.
- Modify the launch script to specify the OVMF you built just now.