Hello, In developing against the altp2m API, I've encountered something I wasn't expecting.
Here's the scenario: 1. Create a new altp2m memory view. Assume we get view ID 1. 2. Change some MFN permissions in view 1. 3. Destroy view 1. 4. Create another altp2m view. Get view ID 1 again. Now, I was expecting that by destroying the view in step 3, all the MFNs in that view would revert back to XENMEM_access_default. However, after completing step 4, I still encounter #VEs based on the permissions I set in step 2. Is this a deliberate design decision? Thanks, Matt -- Matt Leinhos Star Lab https://starlab.io/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
