On Mon, Oct 10, 2022 at 11:58:22PM +0000, Oliver Upton wrote: > I think this further drives the point home -- there's zero need for the > bitmap with dirty ring on x86, so why even support it? The proposal of > ALLOW_BITMAP && DIRTY_RING should be arm64-specific. Any other arch that > needs to dirty memory outside of a vCPU context can opt-in to the > behavior. Yeah that sounds working too, but it'll be slightly hackish as then the user app will need some "#ifdef ARM64" blocks for e.g. sync dirty bitmap. With the new cap the user app can implement the whole ring with generic code. Also more flexible to expose it as generic cap? E.g., one day x86 can enable this too for whatever reason (even though I don't think so..). -- Peter Xu _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
