[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] bogus gfn - mfn - gfn - mfn checks in guest_physmap_add_entry
On 25/11/2010 15:03, "Olaf Hering" <olaf@xxxxxxxxx> wrote: >> The guest_physmap_add_entry code, and the p2m audit code, would be made >> more reliable if, say, alloc_domheap_pages and/or free_domheap_pages >> zapped the m2p entries for MFNs they touched. >> >> I think originally that wasn't done because the alloc is quickly >> followed by another write of the m2p but that's probably over-keen >> optimization. > > Could it be done like that? (not yet compile-tested) > The mfn is probably always valid. If you xap m2p in free_domheap_pages(), you shouldn't need to do it again in alloc_domheap_pages(). -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |