-
Oleksandr Tyshchenko authored
In order to use virtio backends we need to initialize RAM for the xen-mapcache (which is responsible for mapping guest memory using foreign mapping) to work. Calculate and add hi/low memory regions based on machine->ram_size. Use the constants defined in public header arch-arm.h to be aligned with the xen toolstack. While using this machine, the toolstack should then pass real ram_size using "-m" arg. If "-m" is not given, create a QEMU machine without IOREQ and other emulated devices like TPM and VIRTIO. This is done to keep this QEMU machine usable for /etc/init.d/xencommons. Signed-off-by:
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Signed-off-by:
Vikram Garhwal <vikram.garhwal@amd.com>
Reviewed-by:
Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by:
Stefano Stabellini <stefano.stabellini@amd.com>Oleksandr Tyshchenko authoredIn order to use virtio backends we need to initialize RAM for the xen-mapcache (which is responsible for mapping guest memory using foreign mapping) to work. Calculate and add hi/low memory regions based on machine->ram_size. Use the constants defined in public header arch-arm.h to be aligned with the xen toolstack. While using this machine, the toolstack should then pass real ram_size using "-m" arg. If "-m" is not given, create a QEMU machine without IOREQ and other emulated devices like TPM and VIRTIO. This is done to keep this QEMU machine usable for /etc/init.d/xencommons. Signed-off-by:
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Signed-off-by:
Vikram Garhwal <vikram.garhwal@amd.com>
Reviewed-by:
Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by:
Stefano Stabellini <stefano.stabellini@amd.com>
Loading