[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [RFC v3 5/6] xen/arm: Add log_dirty support for ARM
On 05/11/2014 10:28 AM, Julien Grall wrote: These two values don't work for the purpose of dirty tracking. What we need are two fields to track _physical_ memory. lowest_mapped_pfn tracks all memory types, which doesn't apply here.the guest very soon. With this solution there is a 1GB hole between the 2 banks. Your function will therefore stop to work. Furthermore, Xen should not assume that the layout of the guest will always start at GUEST_RAM_BASE. I think you can use max_mapped_pfn and lowest_mapped_pfn here. You may need to modify a bit the signification of it in the p2m code or introduce a new field. Will new fields to track physical ram space acceptable for you? -Wei _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |