From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-s390@vger.kernel.org, xen-devel@lists.xenproject.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
virtualization@lists.linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux390@de.ibm.com
Subject: Re: [PATCH v5 0/3] virtio: Use the DMA API when appropriate
Date: Fri, 19 Sep 2014 14:25:47 -0400 [thread overview]
Message-ID: <20140919182547.GA11449@laptop.dumpdata.com> (raw)
In-Reply-To: <cover.1410931077.git.luto@amacapital.net>
On Tue, Sep 16, 2014 at 10:22:25PM -0700, Andy Lutomirski wrote:
> This fixes virtio on Xen guests as well as on any other platform
> that uses virtio_pci on which physical addresses don't match bus
> addresses.
I can do 'Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>'
but not sure through whom this patch should go through?
>
> This can be tested with:
>
> virtme-run --xen xen --kimg arch/x86/boot/bzImage --console
>
> using virtme from here:
>
> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git
>
> Without these patches, the guest hangs forever. With these patches,
> everything works.
>
> This should be safe on all platforms that I'm aware of. That
> doesn't mean that there isn't anything that I missed.
>
> Applies to net-next.
>
> Changes from v4:
> - Rebased onto net-next.
> - Dropped the sg end mark changes from virtio_net, as that issue
> is solved differently in net-next.
> - virtio_pci does not use the DMA API on powerpc, for reasons that
> are explained in a detailed comment in virtio_ring.
>
> Changes from v3:
> - virtio_pci only asks virtio_ring to use the DMA API if
> !PCI_DMA_BUS_IS_PHYS.
> - Reduce tools/virtio breakage. It's now merely as broken as before
> instead of being even more broken.
> - Drop the sg_next changes -- Rusty's version is better.
>
> Changes from v2:
> - Reordered patches.
> - Fixed a virtio_net OOPS.
>
> Changes from v1:
> - Using the DMA API is optional now. It would be nice to improve the
> DMA API to the point that it could be used unconditionally, but s390
> proves that we're not there yet.
> - Includes patch 4, which fixes DMA debugging warnings from virtio_net.
>
> Andy Lutomirski (3):
> virtio_ring: Support DMA APIs if requested
> virtio_pci: Use the DMA API for virtqueues when possible
> virtio_net: Stop doing DMA from the stack
>
> drivers/lguest/lguest_device.c | 3 +-
> drivers/misc/mic/card/mic_virtio.c | 2 +-
> drivers/net/virtio_net.c | 53 ++++++---
> drivers/remoteproc/remoteproc_virtio.c | 4 +-
> drivers/s390/kvm/kvm_virtio.c | 2 +-
> drivers/s390/kvm/virtio_ccw.c | 4 +-
> drivers/virtio/virtio_mmio.c | 5 +-
> drivers/virtio/virtio_pci.c | 91 ++++++++++++++--
> drivers/virtio/virtio_ring.c | 194 +++++++++++++++++++++++++++------
> include/linux/virtio_ring.h | 1 +
> tools/virtio/linux/dma-mapping.h | 17 +++
> tools/virtio/linux/virtio.h | 1 +
> tools/virtio/virtio_test.c | 2 +-
> tools/virtio/vringh_test.c | 3 +-
> 14 files changed, 314 insertions(+), 68 deletions(-)
> create mode 100644 tools/virtio/linux/dma-mapping.h
>
> --
> 1.9.3
>
prev parent reply other threads:[~2014-09-19 18:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 5:22 [PATCH v5 0/3] virtio: Use the DMA API when appropriate Andy Lutomirski
2014-09-17 5:22 ` [PATCH v5 1/3] virtio_ring: Support DMA APIs if requested Andy Lutomirski
2014-09-17 5:22 ` [PATCH v5 2/3] virtio_pci: Use the DMA API for virtqueues when possible Andy Lutomirski
2014-09-17 12:02 ` Benjamin Herrenschmidt
2014-09-17 14:16 ` Michael S. Tsirkin
2014-09-17 16:07 ` Andy Lutomirski
2014-09-17 16:49 ` David Woodhouse
2014-09-19 21:28 ` Benjamin Herrenschmidt
2014-09-19 21:33 ` Benjamin Herrenschmidt
2014-09-20 5:59 ` Andy Lutomirski
2014-09-21 5:03 ` Benjamin Herrenschmidt
2014-09-21 5:05 ` Benjamin Herrenschmidt
2014-09-21 5:48 ` Andy Lutomirski
2014-09-21 6:01 ` David Woodhouse
2014-09-24 21:41 ` Andy Lutomirski
2014-09-24 21:50 ` Benjamin Herrenschmidt
2014-09-24 21:59 ` Andy Lutomirski
2014-09-24 22:04 ` Benjamin Herrenschmidt
2014-09-24 22:15 ` Andy Lutomirski
2014-09-24 22:38 ` Benjamin Herrenschmidt
2014-09-24 22:49 ` Andy Lutomirski
2014-09-19 21:31 ` Benjamin Herrenschmidt
2014-09-29 18:55 ` Andy Lutomirski
2014-09-29 20:49 ` Benjamin Herrenschmidt
2014-09-29 20:55 ` Andy Lutomirski
2014-09-29 21:06 ` Benjamin Herrenschmidt
2014-09-30 15:38 ` Michael S. Tsirkin
2014-09-30 15:48 ` Andy Lutomirski
2014-09-30 16:19 ` Andy Lutomirski
2014-09-30 17:53 ` Konrad Rzeszutek Wilk
2014-09-30 18:01 ` Andy Lutomirski
2014-10-02 16:36 ` Konrad Rzeszutek Wilk
2014-10-01 6:42 ` Michael S. Tsirkin
2014-09-30 15:53 ` Paolo Bonzini
2014-10-01 7:36 ` Michael S. Tsirkin
2014-09-30 20:05 ` Andy Lutomirski
2014-10-06 9:59 ` Christian Borntraeger
2014-10-06 10:48 ` Benjamin Herrenschmidt
2014-09-17 16:09 ` Ira W. Snyder
2014-09-17 16:15 ` Andy Lutomirski
2014-09-17 5:22 ` [PATCH v5 3/3] virtio_net: Stop doing DMA from the stack Andy Lutomirski
2014-09-19 18:25 ` Konrad Rzeszutek Wilk [this message]
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=20140919182547.GA11449@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=luto@amacapital.net \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.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).