History

vring: Use the DMA API on Xen

Andy Lutomirski committed 10 years ago

Commit 78fe3981 parent 7a5589b1 file · +12 −0Browse files

Unified · Split

drivers/virtio/virtio_ring.c+12−0
@@ -25,6 +25,7 @@ · 24 unmodified lines
25#include <linux/hrtimer.h>25#include <linux/hrtimer.h>
26#include <linux/kmemleak.h>26#include <linux/kmemleak.h>
27#include <linux/dma-mapping.h>27#include <linux/dma-mapping.h>
28#include <xen/xen.h>
28 29
29#ifdef DEBUG30#ifdef DEBUG
30/* For development, we want to crash whenever the ring is screwed. */31/* For development, we want to crash whenever the ring is screwed. */
@@ -136,6 +137,17 @@ struct vring_virtqueue { · 105 unmodified lines
136 137
137static bool vring_use_dma_api(struct virtio_device *vdev)138static bool vring_use_dma_api(struct virtio_device *vdev)
138{139{
140 /*
141 * In theory, it's possible to have a buggy QEMU-supposed
142 * emulated Q35 IOMMU and Xen enabled at the same time. On
143 * such a configuration, virtio has never worked and will
144 * not work without an even larger kludge. Instead, enable
145 * the DMA API if we're a Xen guest, which at least allows
146 * all of the sensible Xen configurations to work correctly.
147 */
148 if (xen_domain())
149 return true;
150
139 return false;151 return false;
140}152}
141 153

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t