From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH qemu 0/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device
Date: Tue, 16 Jan 2018 13:46:14 -0700 [thread overview]
Message-ID: <20180116134614.1aae30b9@w520.home> (raw)
In-Reply-To: <ad143758-227b-55fe-44a6-c62a48f74162@ozlabs.ru>
On Mon, 15 Jan 2018 15:12:07 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 03/01/18 04:51, Paolo Bonzini wrote:
> > On 02/01/2018 06:28, Alexey Kardashevskiy wrote:
> >> This is my current queue of the in-kernel TCE acceleration
> >> enablement.
> >>
> >> Changes since https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg01918.html :
> >> * 3 patches instead of one, one per maintainership area;
> >> * added memory_region_iommu_get_attr();
> >> * removed set_attr() as there is no use for it now;
> >> * folded the chunk in vfio_listener_region_add() under
> >> VFIO_SPAPR_TCE_v2_IOMMU branch as the acceleration is only
> >> enabled when DMA memory is preregistered and this is only supported
> >> by the v2 IOMMU.
> >>
> >> This is based on sha1
> >> ad59cde Cédric Le Goater "target/ppc: more use of the PPC_*() macros".
> >>
> >> Please comment. Thanks.
> >>
> >>
> >>
> >> Alexey Kardashevskiy (3):
> >> memory/iommu: Add get_attr()
> >> vfio/spapr: Use iommu memory region's get_attr()
> >> spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device
> >>
> >> include/exec/memory.h | 22 ++++++++++++++++++++++
> >> target/ppc/kvm_ppc.h | 6 ++++++
> >> hw/ppc/spapr_iommu.c | 19 +++++++++++++++++++
> >> hw/vfio/common.c | 26 ++++++++++++++++++++++++++
> >> memory.c | 13 +++++++++++++
> >> target/ppc/kvm.c | 7 ++++++-
> >> hw/vfio/trace-events | 1 +
> >> 7 files changed, 93 insertions(+), 1 deletion(-)
> >>
> >
> > Alex, if this is okay for you, please pick it up yourself.
>
> Alex, ping?
Yeah, I'll pick these up. Paolo, do you want to throw an explicit Ack
for the first patch? David, R-b/A-b? Thanks,
Alex
next prev parent reply other threads:[~2018-01-16 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 5:28 [Qemu-devel] [PATCH qemu 0/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device Alexey Kardashevskiy
2018-01-02 5:28 ` [Qemu-devel] [PATCH qemu 1/3] memory/iommu: Add get_attr() Alexey Kardashevskiy
2018-01-02 5:28 ` [Qemu-devel] [PATCH qemu 2/3] vfio/spapr: Use iommu memory region's get_attr() Alexey Kardashevskiy
2018-01-02 5:28 ` [Qemu-devel] [PATCH qemu 3/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device Alexey Kardashevskiy
2018-01-02 5:50 ` [Qemu-devel] [PATCH qemu 0/3] " no-reply
2018-01-02 17:51 ` Paolo Bonzini
2018-01-15 4:12 ` Alexey Kardashevskiy
2018-01-16 20:46 ` Alex Williamson [this message]
2018-01-18 5:48 ` David Gibson
2018-01-18 8:13 ` Paolo Bonzini
2018-01-19 4:51 ` David Gibson
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=20180116134614.1aae30b9@w520.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).