9456d91b76
Currently, DM only access /sys/kernel/mm/hugepages/hugepages-2048kB/ entries according to its own huge page requirement. So it could have following race issue: DM1 DM2 read nr pages read nr pages write DM2 nr pages write DM1 nr pages Suppose we should write DM1 + DM2 nr page to kernel sysfs interface to reserve enough huge page (DM1 + DM2). But actually only reserve huge page requested by DM1. Which could trigger one VM can't boot. We can easily hit this issue if we enable multiple UOS auto boot because more than one VM are started at almost same time. We add file lock to make sure huge page reserving in DM atomic. Tracked-On: #3729 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com> Acked-by: Wang Yu <yu1.wang@intel.com> |
||
---|---|---|
.. | ||
arch/x86 | ||
bios | ||
core | ||
hw | ||
include | ||
lib | ||
log | ||
samples | ||
MAINTAINERS | ||
Makefile | ||
README.rst |
README.rst
ACRN Device Model ################# Introduction ============ The ACRN Device Model provides **device sharing** capabilities between the Service OS and Guest OSs. It is a component that is used in conjunction with the `ACRN Hypervisor`_ and this is installed within the Service OS. You can find out more about Project ACRN on the `Project ACRN documentation`_ website. .. _`ACRN Hypervisor`: https://github.com/projectacrn/acrn-hypervisor .. _`Project ACRN documentation`: https://projectacrn.github.io/