On Sun, Jun 27, 2021 at 01:38:14PM +0800, huang...@chinatelecom.cn wrote:
> @@ -370,9 +374,17 @@ static inline void
> cpu_physical_memory_set_dirty_lebitmap(unsigned long *bitmap,
> qatomic_or([DIRTY_MEMORY_VGA][idx][offset], temp);
>
> if
From: Hyman Huang(黄勇)
intrduce DIRTY_MEMORY_DIRTY_RATE dirty bits to tracking vm
dirty page for calculating dirty rate
since dirtyrate and migration may be trigger concurrently,
reusing the exsiting DIRTY_MEMORY_MIGRATION dirty bits seems
not a good choice. introduce a fresh new dirty bits for