[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v3 8/9] hvf: only consider directly writeable memory regions for
From: |
Yan-Jie Wang |
Subject: |
[PATCH v3 8/9] hvf: only consider directly writeable memory regions for dirty-tracking |
Date: |
Wed, 2 Mar 2022 21:04:16 +0800 |
It is no need to dirty-track MMIO regions or other readonly regions.
Before we start or stop to dirty-track a memory region, check the type of
the memory region. The region must be a writeable ram to be dirty-tracked.
Signed-off-by: Yan-Jie Wang <ubzeme@gmail.com>
---
accel/hvf/hvf-mem.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/accel/hvf/hvf-mem.c b/accel/hvf/hvf-mem.c
index 2f70ceb307..60ece20eb4 100644
--- a/accel/hvf/hvf-mem.c
+++ b/accel/hvf/hvf-mem.c
@@ -180,6 +180,12 @@ static void hvf_set_dirty_tracking(MemoryRegionSection
*section, bool on)
{
HVFSlot *slot;
+ if (!memory_region_is_ram(section->mr) ||
+ memory_region_is_rom(section->mr)) {
+ /* do not consider memory regions which are not directly writeable */
+ return;
+ }
+
qemu_mutex_lock(&memlock);
slot = hvf_find_overlap_slot(
--
2.32.0 (Apple Git-132)
- Re: [PATCH v3 3/9] hvf: use correct data types for addresses in memory related functions, (continued)
- [PATCH v3 6/9] hvf: add a lock for memory related functions, Yan-Jie Wang, 2022/03/02
- [PATCH v3 7/9] hvf: use GTree to store memory slots instead of fixed-size array, Yan-Jie Wang, 2022/03/02
- [PATCH v3 5/9] hvf: fix memory dirty-tracking, Yan-Jie Wang, 2022/03/02
- [PATCH v3 9/9] hvf: remove the need to lookup memory slots when clearing dirty-bits, Yan-Jie Wang, 2022/03/02
- [PATCH v3 4/9] hvf: rename struct hvf_slot to HVFSlot, Yan-Jie Wang, 2022/03/02
- [PATCH v3 8/9] hvf: only consider directly writeable memory regions for dirty-tracking,
Yan-Jie Wang <=