From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3tD4gP2DZTzDvHw for ; Wed, 9 Nov 2016 10:06:25 +1100 (AEDT) Date: Tue, 8 Nov 2016 16:06:20 -0700 From: Alex Williamson To: Michael Ellerman Cc: Alexey Kardashevskiy , linuxppc-dev@lists.ozlabs.org, Paul Mackerras , Nicholas Piggin , David Gibson Subject: Re: [PATCH kernel v4 0/4] powerpc/spapr/vfio: Put pages on VFIO container shutdown Message-ID: <20161108160620.54591201@t450s.home> In-Reply-To: <871syml83v.fsf@concordia.ellerman.id.au> References: <1477291990-2872-1-git-send-email-aik@ozlabs.ru> <871syml83v.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 08 Nov 2016 18:54:28 +1100 Michael Ellerman wrote: > Alexey Kardashevskiy writes: > > These patches are to fix a bug when pages stay pinned hours > > after QEMU which requested pinning exited. > > > > Please comment. Thanks. > > > > Alexey Kardashevskiy (4): > > powerpc/iommu: Pass mm_struct to init/cleanup helpers > > powerpc/iommu: Stop using @current in mm_iommu_xxx > > vfio/spapr: Reference mm in tce_container > > powerpc/mm/iommu, vfio/spapr: Put pages on VFIO container shutdown > > > > arch/powerpc/include/asm/mmu_context.h | 20 ++-- > > arch/powerpc/kernel/setup-common.c | 2 +- > > arch/powerpc/mm/mmu_context_book3s64.c | 6 +- > > arch/powerpc/mm/mmu_context_iommu.c | 60 ++++------- > > drivers/vfio/vfio_iommu_spapr_tce.c | 181 ++++++++++++++++++++++----------- > > 5 files changed, 154 insertions(+), 115 deletions(-) > > > Alex, given the diffstat how do you want to merge this? (for 4.10) > > Should I merge it, you merge it, or I can put it in a topic branch? I have an outstanding question on one patch, but otherwise I'd prefer you merge it, I'm not expecting to have anything that would conflict with vfio_iommu_spapr_tce.c and this code is tied pretty tightly with arch code. I'll provide acks depending on how we resolve my question. Thanks, Alex