From: Alex Williamson <alex.williamson@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
Nicholas Piggin <npiggin@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH kernel v4 0/4] powerpc/spapr/vfio: Put pages on VFIO container shutdown
Date: Tue, 8 Nov 2016 16:06:20 -0700 [thread overview]
Message-ID: <20161108160620.54591201@t450s.home> (raw)
In-Reply-To: <871syml83v.fsf@concordia.ellerman.id.au>
On Tue, 08 Nov 2016 18:54:28 +1100
Michael Ellerman <mpe@ellerman.id.au> wrote:
> Alexey Kardashevskiy <aik@ozlabs.ru> 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
next prev parent reply other threads:[~2016-11-08 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 6:53 [PATCH kernel v4 0/4] powerpc/spapr/vfio: Put pages on VFIO container shutdown Alexey Kardashevskiy
2016-10-24 6:53 ` [PATCH kernel v4 1/4] powerpc/iommu: Pass mm_struct to init/cleanup helpers Alexey Kardashevskiy
2016-10-24 6:53 ` [PATCH kernel v4 2/4] powerpc/iommu: Stop using @current in mm_iommu_xxx Alexey Kardashevskiy
2016-10-24 6:53 ` [PATCH kernel v4 3/4] vfio/spapr: Reference mm in tce_container Alexey Kardashevskiy
2016-10-24 7:14 ` Nicholas Piggin
2016-11-08 3:33 ` David Gibson
2016-11-08 22:25 ` Alex Williamson
2016-11-09 0:46 ` David Gibson
2016-10-24 6:53 ` [PATCH kernel v4 4/4] powerpc/mm/iommu, vfio/spapr: Put pages on VFIO container shutdown Alexey Kardashevskiy
2016-10-25 4:44 ` David Gibson
2016-10-25 4:55 ` Alexey Kardashevskiy
2016-10-31 3:13 ` David Gibson
2016-10-31 4:13 ` Alexey Kardashevskiy
2016-10-31 4:23 ` David Gibson
2016-11-02 2:44 ` Alexey Kardashevskiy
2016-11-03 1:02 ` Paul Mackerras
2016-11-08 3:33 ` David Gibson
2016-11-08 3:35 ` David Gibson
2016-11-08 7:54 ` [PATCH kernel v4 0/4] powerpc/spapr/vfio: " Michael Ellerman
2016-11-08 23:06 ` Alex Williamson [this message]
2016-11-10 1:37 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161108160620.54591201@t450s.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).