On Fri, 6 Feb 2015, Wei Liu wrote: > Albeit INVALID_P2M_ENTRY and INVALID_MFN are both ~0UL, conceptually > speaking we should use INVALID_P2M_ENTRY for setting P2M values. > > Signed-off-by: Wei Liu <wei.l...@citrix.com> > Cc: Ian Campbell <ian.campb...@citrix.com> > Cc: Ian Jackson <ian.jack...@eu.citrix.com> > Cc: Stefano Stabellini <stefano.stabell...@eu.citrix.com> > CC: Julien Grall <julien.gr...@citrix.com>
Acked-by: Stefano Stabellini <stefano.stabell...@eu.citrix.com> > tools/libxc/xc_dom_arm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c > index 9b31b1f..c7feca7 100644 > --- a/tools/libxc/xc_dom_arm.c > +++ b/tools/libxc/xc_dom_arm.c > @@ -453,7 +453,7 @@ int arch_setup_meminit(struct xc_dom_image *dom) > if ( dom->p2m_host == NULL ) > return -EINVAL; > for ( pfn = 0; pfn < p2m_size; pfn++ ) > - dom->p2m_host[pfn] = INVALID_MFN; > + dom->p2m_host[pfn] = INVALID_P2M_ENTRY; > > /* setup initial p2m and allocate guest memory */ > for ( i = 0; dom->rambank_size[i] && i < GUEST_RAM_BANKS; i++ ) > -- > 1.9.1 > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
