search for: 4b8dab4960bb

...gt; day. > > Signed-off-by: Andy Lutomirski <luto at kernel.org> > --- > ?drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ > ?1 file changed, 24 insertions(+) > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > index e12e385f7ac3..4b8dab4960bb 100644 > --- a/drivers/virtio/virtio_ring.c > +++ b/drivers/virtio/virtio_ring.c > @@ -25,6 +25,30 @@ > ?#include > ?#include > ? > +/* > + * The interaction between virtio and a possible IOMMU is a mess. > + * > + * On most systems with virtio, physical addresses ma...

...gt; day. > > Signed-off-by: Andy Lutomirski <luto at kernel.org> > --- > ?drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ > ?1 file changed, 24 insertions(+) > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > index e12e385f7ac3..4b8dab4960bb 100644 > --- a/drivers/virtio/virtio_ring.c > +++ b/drivers/virtio/virtio_ring.c > @@ -25,6 +25,30 @@ > ?#include > ?#include > ? > +/* > + * The interaction between virtio and a possible IOMMU is a mess. > + * > + * On most systems with virtio, physical addresses ma...

...et rid of vring_use_dma_api() entirely some day. Signed-off-by: Andy Lutomirski <luto at kernel.org> --- drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index e12e385f7ac3..4b8dab4960bb 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@ -25,6 +25,30 @@ #include <linux/hrtimer.h> #include <linux/kmemleak.h> +/* + * The interaction between virtio and a possible IOMMU is a mess. + * + * On most systems with virtio, physical addresses match...

...-by: Andy Lutomirski <luto at kernel.org> > > --- > > ?drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ > > ?1 file changed, 24 insertions(+) > > > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > > index e12e385f7ac3..4b8dab4960bb 100644 > > --- a/drivers/virtio/virtio_ring.c > > +++ b/drivers/virtio/virtio_ring.c > > @@ -25,6 +25,30 @@ > > ?#include > > ?#include > > ? > > +/* > > + * The interaction between virtio and a possible IOMMU is a mess. > > + * > > + *...

...t;luto at kernel.org> >> > --- >> > drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ >> > 1 file changed, 24 insertions(+) >> > >> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c >> > index e12e385f7ac3..4b8dab4960bb 100644 >> > --- a/drivers/virtio/virtio_ring.c >> > +++ b/drivers/virtio/virtio_ring.c >> > @@ -25,6 +25,30 @@ >> > #include >> > #include >> > >> > +/* >> > + * The interaction between virtio and a possible IOMMU is a mess....

...t;luto at kernel.org> >> > --- >> > drivers/virtio/virtio_ring.c | 24 ++++++++++++++++++++++++ >> > 1 file changed, 24 insertions(+) >> > >> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c >> > index e12e385f7ac3..4b8dab4960bb 100644 >> > --- a/drivers/virtio/virtio_ring.c >> > +++ b/drivers/virtio/virtio_ring.c >> > @@ -25,6 +25,30 @@ >> > #include >> > #include >> > >> > +/* >> > + * The interaction between virtio and a possible IOMMU is a mess....

This switches virtio to use the DMA API on Xen and if requested by module option. This fixes virtio on Xen, and it should break anything because it's off by default on everything except Xen PV on x86. To the Xen people: is this okay? If it doesn't work on other Xen variants (PVH? HVM?), can you submit follow-up patches to fix it? To everyone else: we've waffled on this for way too

This switches virtio to use the DMA API on Xen and if requested by module option. This fixes virtio on Xen, and it should break anything because it's off by default on everything except Xen PV on x86. To the Xen people: is this okay? If it doesn't work on other Xen variants (PVH? HVM?), can you submit follow-up patches to fix it? To everyone else: we've waffled on this for way too