mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-06-29 16:58:10 +00:00
Project ACRN hypervisor
This patch makes the build system of the hypervisor to cache the board and scenario XML files in the build directory and generate C configuration files from them at build time. The C configuration files that are cached in the git repo is no longer used or updated. Paths to these generated files in the prebuild Makefile is updated accordingly. The following targets are introduced or modified. * defconfig: Copy default configuration XMLs to the build directory and generate C configuration files. * oldconfig: No action. * menuconfig: Print a message to redirect users to use the config app and exit. * showconfig: Print the BOARD, SCENARIO and RELEASE configured for the current build. * update_config: No action. * (default): Build the hypervisor with defined configurations. The following variables can be set on the command line to specify the default configuration to be used. * BOARD: Either a name of the target board or a path to a customized board XML. When a board name is specified, the board XML file is expected to be available under misc/acrn-config/xmls/board-xmls. * SCENARIO: Either a name of the scenario of a path to a customized scenario XML. When a scenario name is specified, the scenario XML file is expected to be available under misc/acrn-config/xmls/config-xmls/$(BOARD). * BOARD_FILE: Path to the board XML file to be used. This is now obsoleted as BOARD provides the same functionality. * SCENARIO_FILE: Path to the scenario XML file to be used. This is now obsoleted as BOARD provides the same functionality. BOARD/SCENARIO or BOARD_FILE/SCENARIO_FILE shall be used in pair, and BOARD_FILE/SCENARIO_FILE shall point to valid files when specified. Any violation to those constraints will stop the build with error messages. When BOARD/SCENARIO and BOARD_FILE/SCENARIO_FILE are both defined on the command line, the former takes precedence as the latter are to be obsoleted. Additionally, users can define the RELEASE variable to specify a debug or release build. In case a previous build exists but is configured for a different build type, the build system will automatically update the scenario XML and rebuild the sources. This patch also includes the following tweaks: 1. Do not use `realpath` to process search paths for generated headers. `realpath` only accepts paths of existing files, while the directories for generated headers may not be created at the time the search paths are calculated. 2. Always expect `pci_dev.c` to be in place. 3. HV_CONFIG_* series now encodes absolute paths. v3: * Do not validate BOARD_FILE/SCENARIO_FILE if BOARD/SCENARIO are given. v2: * `defconfig` now also generates the C configuration files. * BOARD/SCENARIO now accept either board/scenario names or XML file paths. * Adapt to the new allocation.xml & unified.xml. * Cleanup names of internal variables in config.mk for brevity. Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com> |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
devicemodel | ||
doc | ||
hypervisor | ||
misc | ||
.checkpatch.conf | ||
.gitignore | ||
CODEOWNERS | ||
LICENSE | ||
Makefile | ||
paths.make | ||
README.rst | ||
VERSION |
Project ACRN Embedded Hypervisor ################################ .. raw:: html <img src="doc/images/ACRN_Logo_PrimaryLockup_COLOR-300x300-1.png" height="175px" align="right"> The open source project ACRN defines a device hypervisor reference stack and an architecture for running multiple software subsystems, managed securely, on a consolidated system by means of a virtual machine manager. It also defines a reference framework implementation for virtual device emulation, called the "ACRN Device Model". The ACRN Hypervisor is a Type 1 reference hypervisor stack, running directly on the bare-metal hardware, and is suitable for a variety of IoT and embedded device solutions. The ACRN hypervisor addresses the gap that currently exists between datacenter hypervisors, and hard partitioning hypervisors. The ACRN hypervisor architecture partitions the system into different functional domains, with carefully selected guest OS sharing optimizations for IoT and embedded devices. .. start_include_here Community Support ***************** The Project ACRN Developer Community includes developers from member organizations and the general community all joining in the development of software within the project. Members contribute and discuss ideas, submit bugs and bug fixes. They also help those in need through the community's forums such as mailing lists and IRC channels. Anyone can join the developer community and the community is always willing to help its members and the User Community to get the most out of Project ACRN. Welcome to the project ARCN community! We're now holding weekly Technical Community Meetings and encourage you to call in and learn more about the project. Meeting information is on the `TCM Meeting page`_ in our `ACRN wiki <https://wiki.projectacrn.org/>`_. .. _TCM Meeting page: https://github.com/projectacrn/acrn-hypervisor/wiki/ACRN-Committee-and-Working-Group-Meetings#technical-community-meetings Resources ********* Here's a quick summary of resources to find your way around the Project ACRN support systems: * **Project ACRN Website**: The https://projectacrn.org website is the central source of information about the project. On this site, you'll find background and current information about the project as well as relevant links to project material. For a quick start, refer to the `Introduction`_ and `Getting Started Guide`_. * **Source Code in GitHub**: Project ACRN source code is maintained on a public GitHub repository at https://github.com/projectacrn/acrn-hypervisor. You'll find information about getting access to the repository and how to contribute to the project in this `Contribution Guide`_ document. * **Documentation**: Project technical documentation is developed along with the project's code, and can be found at https://projectacrn.github.io. Additional documentation is maintained in the `Project ACRN GitHub wiki`_. * **Issue Reporting and Tracking**: Requirements and Issue tracking is done in the Github issues system: https://github.com/projectacrn/acrn-hypervisor/issues. You can browse through the reported issues and submit issues of your own. * **Reporting a Potential Security Vulnerability**: If you have discovered potential security vulnerability in ACRN, please send an e-mail to secure@intel.com. For issues related to Intel Products, please visit https://security-center.intel.com. It is important to include the following details: - The projects and versions affected - Detailed description of the vulnerability - Information on known exploits Vulnerability information is extremely sensitive. Please encrypt all security vulnerability reports using our `PGP key`_. A member of the Intel Product Security Team will review your e-mail and contact you to to collaborate on resolving the issue. For more information on how Intel works to resolve security issues, see: `vulnerability handling guidelines`_. * **Mailing List**: The `Project ACRN Development mailing list`_ is perhaps the most convenient way to track developer discussions and to ask your own support questions to the project ACRN community. There are also specific `ACRN mailing list subgroups`_ for builds, users, and Technical Steering Committee notes, for example. You can read through the message archives to follow past posts and discussions, a good thing to do to discover more about the project. .. _Introduction: https://projectacrn.github.io/latest/introduction/ .. _Getting Started Guide: https://projectacrn.github.io/latest/getting-started/ .. _Contribution Guide: https://projectacrn.github.io/latest/contribute.html .. _Project ACRN GitHub wiki: https://github.com/projectacrn/acrn-hypervisor/wiki .. _PGP Key: https://www.intel.com/content/www/us/en/security-center/pgp-public-key.html .. _vulnerability handling guidelines: https://www.intel.com/content/www/us/en/security-center/vulnerability-handling-guidelines.html .. _Project ACRN Development mailing list: https://lists.projectacrn.org/g/acrn-dev .. _ACRN mailing list subgroups: https://lists.projectacrn.org/g/main/subgroups