From 0c360b5e516e0cb6233d261d7a7877bcb5ec1676 Mon Sep 17 00:00:00 2001 From: Diogo Costa Date: Mon, 2 Dec 2024 14:23:19 +0000 Subject: [PATCH] fix(doc): add note regarding to MMIO mapping Signed-off-by: Diogo Costa --- source/bao_hyp/config.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/bao_hyp/config.rst b/source/bao_hyp/config.rst index ad7a6d8..dbba7a4 100644 --- a/source/bao_hyp/config.rst +++ b/source/bao_hyp/config.rst @@ -483,6 +483,16 @@ where: - ``iommu.fq_irq_id`` [mandatory if IOMMU is available] - the Fault Queue interrupt ID (the current implementation assumes this is a wired interrupt); +.. note:: + + When mapping MMIO regions for guests, the memory regions associated with the GIC (Generic + Interrupt Controller) must be excluded. Mapping these regions can lead to conflicts or incorrect + behavior, as they are typically managed by Bao through trap-and-emulate mechanisms. + + For instance, if a large MMIO range includes the GIC, the range should be split to create a + "hole" for the GIC. This ensures that GIC memory regions (or their equivalents in other + architectures, such as RISC-V) are not directly mapped into the guest's virtual address space. + CPU Affinity ************