github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-08-03 17:31:42 +00:00
Code Issues Projects Releases Wiki Activity

doc: edit 0.2 release notes

Browse Source 
Followup #1281 update with some spelling and formatting fixes

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2018-09-18 09:16:47 -07:00 committed by David Kinder
parent 737c29fad8
commit 40dfd3fc24
1 changed files with 60 additions and 65 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

125
doc/release_notes_0.2.rst
View File

@ -22,32 +22,35 @@ VT-x, VT-d
Based on Intel VT-x virtualization technology, ACRN emulates a virtual Based on Intel VT-x virtualization technology, ACRN emulates a virtual
CPU with core partition and simple schedule. VT-d provides hardware CPU with core partition and simple schedule. VT-d provides hardware
support for isolating and restricting device accesses to the owner of support for isolating and restricting device accesses to the owner of
the partition managing the device. It allows assigning I/O devices to a VM, the partition managing the device. It allows assigning I/O devices to a
and extending the protection and isolation properties of VMs for I/O operations. VM, and extending the protection and isolation properties of VMs for I/O
operations.
PIC/IOAPIC/MSI/MSI-X/PCI/LAPIC PIC/IOAPIC/MSI/MSI-X/PCI/LAPIC
================================ ================================
ACRN hypervisor supports virtualized APIC-V/EPT/IOAPIC/LAPIC functionality. ACRN hypervisor supports virtualized APIC-V/EPT/IOAPIC/LAPIC
functionality.
Ethernet Ethernet
================ ================
ACRN hypervisor supports virtualized Ethernet functionality. Ethernet Mediator is ACRN hypervisor supports virtualized Ethernet functionality. Ethernet
executed in the Service OS and provides packet forwarding between the physical Mediator is executed in the Service OS and provides packet forwarding
networking devices (Ethernet, Wi-Fi, etc.) and virtual devices in the Guest between the physical networking devices (Ethernet, Wi-Fi, etc.) and
VMs(also called "User OS"). Virtual Ethernet device could be shared by Linux, virtual devices in the Guest VMs(also called "User OS"). Virtual
Android, and Service OS guests for regular (i.e. non-AVB) traffic. All hypervisor Ethernet device could be shared by Linux, Android, and Service OS guests
para-virtualized I/O is implemented using the VirtIO specification Ethernet pass-through. for regular (i.e. non-AVB) traffic. All hypervisor para-virtualized I/O
is implemented using the VirtIO specification Ethernet pass-through.
Storage (eMMC) Storage (eMMC)
================ ================
ACRN hypervisor supports virtualized non-volatile R/W storage for the Service ACRN hypervisor supports virtualized non-volatile R/W storage for the
OS and Guest OS instances, supporting VM private storage and/or storage shared Service OS and Guest OS instances, supporting VM private storage and/or
between Guest OS instances. storage shared between Guest OS instances.
USB (xDCI) USB (xDCI)
================ ================
ACRN hypervisor supports virtualized assignment of all USB xHCI and/or xDCI ACRN hypervisor supports virtualized assignment of all USB xHCI and/or
controllers to a Guest OS from the platform. xDCI controllers to a Guest OS from the platform.
USB Mediator (xHCI and DRD) USB Mediator (xHCI and DRD)
=========================== ===========================
@ -55,15 +58,16 @@ ACRN hypervisor supports a virtualized USB Mediator.
CSME CSME
================ ================
ACRN hypervisor supports a CSME to a single Linux, Android, or RTOS guest or ACRN hypervisor supports a CSME to a single Linux, Android, or RTOS
the Service OS even when in a virtualized environment. guest or the Service OS even when in a virtualized environment.
WiFi WiFi
================ ================
ACRN hypervisor supports the passthrough assignment of the WiFi subsystem to the IVI, ACRN hypervisor supports the passthrough assignment of the WiFi
enables control of the WiFi as an in-vehicle hotspot for 3rd party devices, subsystem to the IVI, enables control of the WiFi as an in-vehicle
provides 3rd party device applications access to the vehicle, hotspot for 3rd party devices, provides 3rd party device applications
and provides access of 3rd party devices to the TCU provided connectivity. access to the vehicle, and provides access of 3rd party devices to the
TCU provided connectivity.
IPU (MIPI-CS2, HDMI-in) IPU (MIPI-CS2, HDMI-in)
======================== ========================
@ -72,16 +76,16 @@ guest OS, without sharing.
Bluetooth Bluetooth
================ ================
ACRN hypervisor supports bluetooth controller passthrough to a single Guest OS (IVI). ACRN hypervisor supports bluetooth controller passthrough to a single
Guest OS (IVI).
GPU – Preemption GPU – Preemption
================== ==================
GPU Preemption is one typical automotive use case which requires GPU Preemption is one typical automotive use case which requires the
the system to preempt GPU resources occupied by lower priority system to preempt GPU resources occupied by lower priority workloads.
workloads. This is done to ensure performance of the most critical This is done to ensure performance of the most critical workload can be
workload can be achieved. Three different schedulers for the GPU achieved. Three different schedulers for the GPU are involved: i915 UOS
are involved: i915 UOS scheduler, Mediator GVT scheduler, and scheduler, Mediator GVT scheduler, and i915 SOS scheduler.
i915 SOS scheduler.
GPU – display surface sharing via Hyper DMA GPU – display surface sharing via Hyper DMA
============================================ ============================================
@ -100,53 +104,44 @@ ACRN hypervisor supports S3 feature, partially enabled in LaaG.
Fixed Issues Fixed Issues
************ ************
:acrn-issue:`663` - Black screen displayed after booting SOS/UOS * :acrn-issue:`663` - Black screen displayed after booting SOS/UOS
* :acrn-issue:`676` - Hypervisor and DM version numbers incorrect
:acrn-issue:`676` - Hypervisor and DM version numbers incorrect * :acrn-issue:`1126` - VPCI coding style and bugs fixes for partition mode
* :acrn-issue:`1125` - VPCI coding style and bugs fixes found in integration testing for partition mode
:acrn-issue:`1126` - VPCI coding style and bugs fixes for partition mode * :acrn-issue:`1101` - missing acrn_mngr.h
* :acrn-issue:`1071` - hypervisor cannot boot on skylake i5-6500
:acrn-issue:`1125` - VPCI coding style and bugs fixes found in integration testing for partition mode * :acrn-issue:`1003` - CPU: cpu info is not correct
* :acrn-issue:`971` - acrncrashlog functions need to be enhance
:acrn-issue:`1101` - missing acrn_mngr.h * :acrn-issue:`843` - ACRN boot failure
* :acrn-issue:`721` - DM for IPU mediation
:acrn-issue:`1071` - hypervisor cannot boot on skylake i5-6500 * :acrn-issue:`707` - Issues found with instructions for using Ubuntu as SOS
* :acrn-issue:`706` - Invisible mouse cursor in UOS
:acrn-issue:`1003` - CPU: cpu info is not correct * :acrn-issue:`424` - Clear Linux desktop GUI of SOS fails to launch
:acrn-issue:`971` - acrncrashlog funcitons need to be enhance
:acrn-issue:`843` - ACRN boot failure
:acrn-issue:`721` - DM for IPU mediation
:acrn-issue:`707` - Issues found with instructions for using Ubuntu as SOS
:acrn-issue:`706` - Invisible mouse cursor in UOS
:acrn-issue:`424` - ClearLinux desktop GUI of SOS fails to launch
Known Issues Known Issues
************ ************
:acrn-issue:`677` - SSD Disk ID not consistent between SOS/UOS :acrn-issue:`677` - SSD Disk ID not consistent between SOS/UOS
The SSD disk ID in the UOS is not the same as in the SOS when The SSD disk ID in the UOS is not the same as in the SOS when the SSD
the SSD device is pass-through to the UOS. The ID is also changing after device is passed-through to the UOS (it should be). The ID is also
a reboot. **Impact:** There is no impact to functionality. changing after a reboot (it shouldn't). **Impact:** There is no impact
**Workaround:** None.The issue will be fixed in the next release. to functionality. **Workaround:** None. The issues will be fixed in the
next release.
:acrn-issue:`1268` - GPU hang happened when running GfxBench Car Chase in SOS and UOS. :acrn-issue:`1268` - GPU hangs when running GfxBench Car Chase in SOS and UOS.
There were always "GPU HANG" log info printed in dmesg log in SOS and UOS and A "GPU HANG" log messages is printed in the dmesg log in SOS and UOS and
failed to load GfxBench Car Chase animation in HDMI & VGA monitors. is fails to load GfxBench Car Chase animation in HDMI and VGA monitors.
**Impact:** Car Chase may stop running after the GPU hang, but not block other Gfx apps. **Impact:** Car Chase may stop running after the GPU hangs, but does not
**Workaround:** None. The issue will be fixed in the next release. block other Gfx apps. **Workaround:** None. The issue will be fixed in
the next release.
:acrn-issue:`1270` - SOS and UOS can play video but no display video animation output on monitor. :acrn-issue:`1270` - SOS and UOS play video but don't display video animation output on monitor.
Video does not display in SOS and UOS. No animation displayed with timer keep running. **Impact:** Video does not display in SOS and UOS. Animation is not displayed with
There is no video animation on monitor screen when playing video in SOS or UOS. the running timer. **Impact:** There is no video animation on monitor
**Workaround:** None. The issue will be fixed in the next release. screen when playing video in SOS or UOS. **Workaround:** None. The
issue will be fixed in the next release.
.. comment .. comment