From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, mst@redhat.com
Cc: xen-devel@lists.xenproject.org,
Andy Lutomirski <luto@amacapital.net>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Xen-devel] [PATCH RFC 0/3] Xen on Virtio
Date: Mon, 14 Dec 2015 14:00:05 +0000 [thread overview]
Message-ID: <566ECB65.3060509@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1512071555590.24652@kaball.uk.xensource.com>
On 07/12/15 16:19, Stefano Stabellini wrote:
> Hi all,
>
> this patch series introduces support for running Linux on top of Xen
> inside a virtual machine with virtio devices (nested virt scenario).
> The problem is that Linux virtio drivers use virt_to_phys to get the
> guest pseudo-physical addresses to pass to the backend, which doesn't
> work as expected on Xen.
>
> Switching the virtio drivers to the dma APIs (dma_alloc_coherent,
> dma_map/unmap_single and dma_map/unmap_sg) would solve the problem, as
> Xen support in Linux provides an implementation of the dma API which
> takes care of the additional address conversions. However using the dma
> API would increase the complexity of the non-Xen case too. We would also
> need to keep track of the physical or virtual address in addition to the
> dma address for each vring_desc to be able to free the memory in
> detach_buf (see patch #3).
>
> Instead this series adds few obvious checks to perform address
> translations in a couple of key places, without changing non-Xen code
> paths. You are welcome to suggest improvements or alternative
> implementations.
Andy Lutomirski also looked at this. Andy what happened to this work?
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, <mst@redhat.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [Xen-devel] [PATCH RFC 0/3] Xen on Virtio
Date: Mon, 14 Dec 2015 14:00:05 +0000 [thread overview]
Message-ID: <566ECB65.3060509@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1512071555590.24652@kaball.uk.xensource.com>
On 07/12/15 16:19, Stefano Stabellini wrote:
> Hi all,
>
> this patch series introduces support for running Linux on top of Xen
> inside a virtual machine with virtio devices (nested virt scenario).
> The problem is that Linux virtio drivers use virt_to_phys to get the
> guest pseudo-physical addresses to pass to the backend, which doesn't
> work as expected on Xen.
>
> Switching the virtio drivers to the dma APIs (dma_alloc_coherent,
> dma_map/unmap_single and dma_map/unmap_sg) would solve the problem, as
> Xen support in Linux provides an implementation of the dma API which
> takes care of the additional address conversions. However using the dma
> API would increase the complexity of the non-Xen case too. We would also
> need to keep track of the physical or virtual address in addition to the
> dma address for each vring_desc to be able to free the memory in
> detach_buf (see patch #3).
>
> Instead this series adds few obvious checks to perform address
> translations in a couple of key places, without changing non-Xen code
> paths. You are welcome to suggest improvements or alternative
> implementations.
Andy Lutomirski also looked at this. Andy what happened to this work?
David
next prev parent reply other threads:[~2015-12-14 14:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 16:19 [PATCH RFC 0/3] Xen on Virtio Stefano Stabellini
2015-12-07 16:19 ` [PATCH RFC 1/3] xen: export xen_phys_to_bus, xen_bus_to_phys and xen_virt_to_bus Stefano Stabellini
2015-12-07 16:19 ` Stefano Stabellini
2015-12-14 14:12 ` [Xen-devel] " David Vrabel
2015-12-14 14:12 ` David Vrabel
2015-12-14 14:12 ` David Vrabel
2015-12-07 16:19 ` Stefano Stabellini
2015-12-07 16:19 ` [PATCH RFC 2/3] xen/virtio: allocate a contiguous region to be use as virtio queue Stefano Stabellini
2015-12-07 16:19 ` Stefano Stabellini
2015-12-07 16:19 ` Stefano Stabellini
2015-12-07 16:19 ` [PATCH RFC 3/3] xen/virtio_ring: introduce cpu_to_virtio_addr and virtio_addr_to_cpu Stefano Stabellini
2015-12-07 16:19 ` Stefano Stabellini
2015-12-07 16:19 ` Stefano Stabellini
2015-12-14 14:00 ` David Vrabel [this message]
2015-12-14 14:00 ` [Xen-devel] [PATCH RFC 0/3] Xen on Virtio David Vrabel
2015-12-14 14:12 ` Michael S. Tsirkin
2015-12-14 14:12 ` [Xen-devel] " Michael S. Tsirkin
2015-12-14 14:12 ` Michael S. Tsirkin
2015-12-14 18:27 ` Andy Lutomirski
2015-12-15 12:13 ` Stefano Stabellini
2015-12-15 12:13 ` [Xen-devel] " Stefano Stabellini
2015-12-15 12:13 ` Stefano Stabellini
2015-12-15 16:45 ` Andy Lutomirski
2015-12-15 20:44 ` Michael S. Tsirkin
2015-12-15 20:44 ` [Xen-devel] " Michael S. Tsirkin
2015-12-15 20:44 ` Michael S. Tsirkin
2015-12-15 16:45 ` Andy Lutomirski
2015-12-15 16:45 ` Andy Lutomirski
2015-12-15 20:40 ` Michael S. Tsirkin
2015-12-15 20:40 ` [Xen-devel] " Michael S. Tsirkin
2015-12-15 20:40 ` Michael S. Tsirkin
2016-01-11 23:03 ` Andy Lutomirski
2016-01-11 23:03 ` Andy Lutomirski
2016-01-11 23:03 ` Andy Lutomirski
2015-12-14 18:27 ` [Xen-devel] " Andy Lutomirski
2015-12-14 18:27 ` Andy Lutomirski
2015-12-14 14:00 ` David Vrabel
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=566ECB65.3060509@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mst@redhat.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.