OrgACRN
/
acrn-hypervisor
mirror of https://github.com/projectacrn/acrn-hypervisor.git
1
0
Fork 0
Code Issues Releases Wiki Activity

doc: update our FAQ section 

Update our FAQ section by deleting outdated and obsolete information.

Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
This commit is contained in:
Geoffroy Van Cutsem 2021-02-23 13:25:03 +01:00 committed by David Kinder
parent 722bf55c57
commit 31a9d053f8
1 changed files with 3 additions and 67 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

70
doc/faq.rst
View File

@ -13,7 +13,7 @@ Here are some frequently asked questions about the ACRN project.
What Hardware Does ACRN Support?
********************************
ACRN runs on Intel boards, as documented in
ACRN runs on Intel-based boards, as documented in
our :ref:`hardware` documentation.
.. _config_32GB_memory:
@ -30,72 +30,8 @@ option settings for details:
* :option:`hv.MEMORY.UOS_RAM_SIZE`
* :option:`hv.MEMORY.HV_RAM_SIZE`
For example, if the Intel NUC's physical memory size is 32G, you may follow these steps
to make the new UEFI ACRN hypervisor, and then deploy it onto the Intel NUC to boot
the ACRN Service VM with the 32G memory size.
#. Use ``make menuconfig`` to change the ``RAM_SIZE``::
$ cd acrn-hypervisor
$ make menuconfig -C hypervisor BOARD=nuc7i7dnb
#. Navigate to these items and then change the value as given below::
(0x0f000000) Size of the RAM region used by the hypervisor
(0x800000000) Size of the physical platform RAM
(0x800000000) Size of the Service OS (SOS) RAM
#. Press :kbd:`S` and then :kbd:`Enter` to save the ``.config`` to the default directory:
``acrn-hypervisor/hypervisor/build/.config``
#. Press :kbd:`ESC` to leave the menu.
#. Then continue building the ACRN Service VM as usual.
How to Modify the Default Display Output for a User VM?
*******************************************************
Apollo Lake HW has three pipes and each pipe can have three or four planes which
help to display the overlay video. The hardware can support up to 3 monitors
simultaneously. Some parameters are available to control how display monitors
are assigned between the Service VM and User VM(s), simplifying the assignment policy and
providing configuration flexibility for the pipes and planes for various IoT
scenarios. This is known as the **plane restriction** feature.
* ``i915.avail_planes_per_pipe``: for controlling how planes are assigned to the
pipes
* ``i915.domain_plane_owners``: for controlling which domain (VM) will have
access to which plane
Refer to :ref:`GVT-g-kernel-options` for detailed parameter descriptions.
In the default configuration, pipe A is assigned to the Service VM and pipes B and C
are assigned to the User VM, as described by these parameters:
* Service VM::
i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000
* User VM::
i915.avail_planes_per_pipe=0x0070F00
To assign pipes A and B to the User VM, while pipe C is assigned to the Service VM, use
these parameters:
* Service VM::
i915.avail_planes_per_pipe=0x070101
i915.domain_plane_owners=0x000011111111
* User VM::
i915.avail_planes_per_pipe=0x000F0F
.. note:: The Service VM always has at least one plane per pipe. This is
intentional, and the driver will enforce this if the parameters do not
do this.
Check the :ref:`acrn_configuration_tool` for more information on how
to adjust these settings.
Why Does ACRN Need to Know How Much RAM the System Has?
*******************************************************