[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v6 12/15] x86/smpboot: switch pl*e to use new APIs in clone_mapping
On 24.04.2020 16:09, Hongyan Xia wrote: > From: Wei Liu <wei.liu2@xxxxxxxxxx> Nit: Why the emphasis on pl*e in the title? Is there anything left unconverted in the function? IOW how about "switch clone_mapping() to new page table APIs"? > --- a/xen/arch/x86/smpboot.c > +++ b/xen/arch/x86/smpboot.c > @@ -672,9 +672,9 @@ static int clone_mapping(const void *ptr, root_pgentry_t > *rpt) > { > unsigned long linear = (unsigned long)ptr, pfn; > unsigned int flags; > - l3_pgentry_t *pl3e; > - l2_pgentry_t *pl2e; > - l1_pgentry_t *pl1e; > + l3_pgentry_t *pl3e = NULL; > + l2_pgentry_t *pl2e = NULL; > + l1_pgentry_t *pl1e = NULL; The latter two need initializers, yes, but why pl3e? > @@ -689,8 +689,8 @@ static int clone_mapping(const void *ptr, root_pgentry_t > *rpt) > (linear >= XEN_VIRT_END && linear < DIRECTMAP_VIRT_START) ) > return -EINVAL; > > - pl3e = l4e_to_l3e(idle_pg_table[root_table_offset(linear)]) + > - l3_table_offset(linear); > + pl3e = map_l3t_from_l4e(idle_pg_table[root_table_offset(linear)]); > + pl3e += l3_table_offset(linear); By keeping original style (a single assignment) you'd have slightly less of a diff, and I think keeping original style where it's not colliding with any of our rules is generally a good idea. Doing so won't even make you hit the slightly flawed definition of map_l3t_from_l4e() at al (missing outer parentheses). I notice you do so ... > @@ -702,7 +702,7 @@ static int clone_mapping(const void *ptr, root_pgentry_t > *rpt) > } > else > { > - pl2e = l3e_to_l2e(*pl3e) + l2_table_offset(linear); > + pl2e = map_l2t_from_l3e(*pl3e) + l2_table_offset(linear); > flags = l2e_get_flags(*pl2e); > ASSERT(flags & _PAGE_PRESENT); > if ( flags & _PAGE_PSE ) > @@ -713,7 +713,7 @@ static int clone_mapping(const void *ptr, root_pgentry_t > *rpt) > } > else > { > - pl1e = l2e_to_l1e(*pl2e) + l1_table_offset(linear); > + pl1e = map_l1t_from_l2e(*pl2e) + l1_table_offset(linear); ... in both of these cases. > @@ -724,48 +724,61 @@ static int clone_mapping(const void *ptr, > root_pgentry_t *rpt) > } > } > > + UNMAP_DOMAIN_PAGE(pl1e); > + UNMAP_DOMAIN_PAGE(pl2e); > + UNMAP_DOMAIN_PAGE(pl3e); > + > if ( !(root_get_flags(rpt[root_table_offset(linear)]) & _PAGE_PRESENT) ) > { > - pl3e = alloc_xen_pagetable(); > - if ( !pl3e ) > + mfn_t l3mfn = alloc_xen_pagetable_new(); > + > + if ( mfn_eq(l3mfn, INVALID_MFN) ) > goto out; > + > + pl3e = map_domain_page(l3mfn); Seeing this recur (from other patches) I wonder whether we wouldn't better make map_domain_page() accept INVALID_MFN and return NULL in this case. In cases like the one here it would eliminate the need for several local variables. Of course the downside of this is that then we'll have to start checking map_domain_page()'s return value. A middle ground could be to have void *alloc_mapped_pagetable(mfn_t *mfn); allowing to pass in NULL if the MFN is of no interest. > @@ -781,6 +794,9 @@ static int clone_mapping(const void *ptr, root_pgentry_t > *rpt) > > rc = 0; > out: > + UNMAP_DOMAIN_PAGE(pl1e); > + UNMAP_DOMAIN_PAGE(pl2e); > + UNMAP_DOMAIN_PAGE(pl3e); > return rc; > } I don't think the writing of NULL into the variables is necessary here. And if the needed if()-s are of concern, then perhaps we should consider making unmap_domain_page() finally accept NULL as input? Jan
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |