0df4f266b3
Based on include/xen/mm.h [1], Linux is mistakenly using MFN when GFN is meant, I suspect this is because the first support for Xen was for PV. This resulted in some misimplementation of helpers on ARM and confused developers about the expected behavior. For instance, with pfn_to_mfn, we expect to get an MFN based on the name. Although, if we look at the implementation on x86, it's returning a GFN. For clarity and avoid new confusion, replace any reference to mfn with gfn in any helpers used by PV drivers. The x86 code will still keep some reference of pfn_to_mfn which may be used by all kind of guests No changes as been made in the hypercall field, even though they may be invalid, in order to keep the same as the defintion in xen repo. Note that page_to_mfn has been renamed to xen_page_to_gfn to avoid a name to close to the KVM function gfn_to_page. Take also the opportunity to simplify simple construction such as pfn_to_mfn(page_to_pfn(page)) into xen_page_to_gfn. More complex clean up will come in follow-up patches. [1] http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=e758ed14f390342513405dd766e874934573e6cb Signed-off-by: Julien Grall <julien.grall@citrix.com> Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Acked-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
23 lines
464 B
C
23 lines
464 B
C
#ifndef _XEN_PAGE_H
|
|
#define _XEN_PAGE_H
|
|
|
|
#include <asm/xen/page.h>
|
|
|
|
static inline unsigned long xen_page_to_gfn(struct page *page)
|
|
{
|
|
return pfn_to_gfn(page_to_pfn(page));
|
|
}
|
|
|
|
struct xen_memory_region {
|
|
unsigned long start_pfn;
|
|
unsigned long n_pfns;
|
|
};
|
|
|
|
#define XEN_EXTRA_MEM_MAX_REGIONS 128 /* == E820MAX */
|
|
|
|
extern __initdata
|
|
struct xen_memory_region xen_extra_mem[XEN_EXTRA_MEM_MAX_REGIONS];
|
|
|
|
extern unsigned long xen_released_pages;
|
|
|
|
#endif /* _XEN_PAGE_H */
|