From: David Hildenbrand <da...@redhat.com> Let's update the documentation, making it clearer what the semantics of memory_region_is_mapped() actually are.
Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com> Reviewed-by: Peter Xu <pet...@redhat.com> Signed-off-by: David Hildenbrand <da...@redhat.com> Message-Id: <20211102164317.45658-4-da...@redhat.com> Signed-off-by: Philippe Mathieu-Daudé <f4...@amsat.org> --- include/exec/memory.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/include/exec/memory.h b/include/exec/memory.h index fea1a493b9c..63be794a067 100644 --- a/include/exec/memory.h +++ b/include/exec/memory.h @@ -2297,7 +2297,8 @@ bool memory_region_present(MemoryRegion *container, hwaddr addr); /** * memory_region_is_mapped: returns true if #MemoryRegion is mapped - * into any address space. + * into another memory region, which does not necessarily imply that it is + * mapped into an address space. * * @mr: a #MemoryRegion which should be checked if it's mapped */ -- 2.34.1
