[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] Don't take the domain lock for p2m operations.
> P2M ops are covered by their own locks, and these uses of the domain > lock are relics of shadow-v1 code. > > Signed-off-by: Tim Deegan <tim@xxxxxxx> Reviewed-by: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx> What about other uses of the domain lock? Should a subsequent patch be cut, or this one expanded? By my count, the following uses of the domain lock in mm code could be abolished or replaced by the p2m lock: * ARM's xenmem_add_to_physmap_once * emulation of cr3 write (traps.c) * And possibly x86's do_set_gdt, although I'm unclear about it That would leave the domain lock only to protect vcpu related ops. My 0.02 Andres > --- > xen/arch/x86/mm.c | 9 +++------ > xen/common/memory.c | 4 ---- > 2 files changed, 3 insertions(+), 10 deletions(-) > > diff --git a/xen/arch/x86/mm.c b/xen/arch/x86/mm.c > index c00841c..e7f0e13 100644 > --- a/xen/arch/x86/mm.c > +++ b/xen/arch/x86/mm.c > @@ -4596,11 +4596,6 @@ static int xenmem_add_to_physmap_once( > return -EINVAL; > } > > - domain_lock(d); > - > - if ( page ) > - put_page(page); > - > /* Remove previously mapped page if it was present. */ > prev_mfn = mfn_x(get_gfn(d, xatp->gpfn, &p2mt)); > if ( mfn_valid(prev_mfn) ) > @@ -4631,7 +4626,9 @@ static int xenmem_add_to_physmap_once( > if ( xatp->space == XENMAPSPACE_gmfn || > xatp->space == XENMAPSPACE_gmfn_range ) > put_gfn(d, gfn); > - domain_unlock(d); > + > + if ( page ) > + put_page(page); > > return rc; > } > diff --git a/xen/common/memory.c b/xen/common/memory.c > index 06a0d0a..50b740f 100644 > --- a/xen/common/memory.c > +++ b/xen/common/memory.c > @@ -693,8 +693,6 @@ long do_memory_op(unsigned long cmd, > XEN_GUEST_HANDLE_PARAM(void) arg) > return rc; > } > > - domain_lock(d); > - > page = get_page_from_gfn(d, xrfp.gpfn, NULL, P2M_ALLOC); > if ( page ) > { > @@ -704,8 +702,6 @@ long do_memory_op(unsigned long cmd, > XEN_GUEST_HANDLE_PARAM(void) arg) > else > rc = -ENOENT; > > - domain_unlock(d); > - > rcu_unlock_domain(d); > > break; > -- > 1.7.10.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |