On 24.01.2020 16:31, Paul Durrant wrote: > vmx_alloc_vlapic_mapping() currently contains some very odd looking code > that allocates a MEMF_no_owner domheap page and then shares with the guest > as if it were a xenheap page. This then requires vmx_free_vlapic_mapping() > to call a special function in the mm code: free_shared_domheap_page(). > > By using a MEMF_no_refcount domheap page instead, the odd looking code in > vmx_alloc_vlapic_mapping() can simply use get_page_and_type() to set up a > writable mapping before insertion in the P2M and vmx_free_vlapic_mapping() > can simply release the page using put_page_alloc_ref() followed by > put_page_and_type(). This then allows free_shared_domheap_page() to be > purged. > > Signed-off-by: Paul Durrant <pdurr...@amazon.com>
Reviewed-by: Jan Beulich <jbeul...@suse.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
