Project ACRN hypervisor
Go to file
Qi Yadong 4c8c7cc8d1 trusty: initialize tsc_offset to zero
Per trusty design, trusty requires a monotonic increasing
secure tick(TSC) at run time. This secure tick will used
to mitigate password/pin force attack, control key expiration,
etc.

Currently, the TSC_OFFSET is enabled. And guest will got
(host_tsc + tsc_offset) when execute rdtsc/rdtscp/rdmsr to
aquire tsc value. The host_tsc is always keeping increasing
during the runtime.

So initialize tsc_offset of trusty to 0 will ensure the
secure tick feature.

Signed-off-by: Qi Yadong <yadong.qi@intel.com>
Acked-by: Eddie Dong <eddie.dong@intel.com>
2018-04-09 12:37:02 +08:00
.travis-dockerfiles Travis CI: enable Ubuntu 16.04 and Fedora 26 testing 2018-04-06 22:28:46 +08:00
arch/x86 trusty: initialize tsc_offset to zero 2018-04-09 12:37:02 +08:00
boot UEFI: bug fix on delivering RSDP 2018-03-30 19:48:46 +08:00
bsp UEFI: get the guest entry address explicitly 2018-04-08 11:14:59 +08:00
common HV: add hypercall interface of get vcpu state data 2018-04-08 16:54:42 +08:00
debug replace malloc and memset with calloc 2018-04-06 12:34:26 +08:00
Documentation UEFI: update documentation 2018-03-30 19:48:46 +08:00
include ept: change eptp to PA 2018-04-09 12:36:09 +08:00
lib Rename TIME_MS_DELTA to CYCLES_PER_MS 2018-03-29 14:54:23 +08:00
.gitignore .gitignore: add 2 entries to ignore version.h file if present 2018-03-21 10:02:27 +08:00
.travis.yml Travis CI: enable Ubuntu 16.04 and Fedora 26 testing 2018-04-06 22:28:46 +08:00
license_header initial import 2018-03-07 21:05:38 +08:00
MAINTAINERS update home page information 2018-04-02 10:18:59 +08:00
Makefile HV: load cpu px data in boot 2018-04-08 16:54:42 +08:00
README.rst initial import 2018-03-07 21:05:38 +08:00

Embedded-Hypervisor
###################

This open source embedded hypervisor defines a software architecture for
running multiple software subsystems managed securely on a consolidated
system (by means of a virtual machine manager), and defines a reference
framework Device Model implementation for devices emulation

This embedded hypervisor is type-1 reference hypervisor, running
directly on the system hardware. It can be used for building software
defined cockpit (SDC) or In-Vehicle Experience (IVE) solutions running
on Intel Architecture Apollo Lake platforms. As a reference
implementation, it provides the basis for embedded hypervisor vendors to
build solutions with an open source reference I/O mediation solution,
and provides auto makers a reference software stack for SDC usage.

This embedded hypervisor is able to support both Linux* and Android* as
a Guest OS, managed by the hypervisor, where applications can run.

This embedded hypervisor is a partitioning hypervisor reference stack,
also suitable for non-automotive IoT & embedded device solutions. It
will be addressing the gap that currently exists between datacenter
hypervisors, hard partitioning hypervisors, and select industrial
applications.  Extending the scope of this open source embedded
hypervisor relies on the involvement of community developers like you!