On Monday 12 November 2007 16:20:01 Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to our structure so
that every DMA access goes through us. (This is the reason this only
works for 64-bit guest. 32-bit guest
On Mon, Nov 12, 2007 at 05:26:24PM +0530, Amit Shah wrote:
On Monday 12 November 2007 16:20:01 Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to our structure so
that every DMA access goes through us. (This
On Monday 12 November 2007 19:02:07 Muli Ben-Yehuda wrote:
On Mon, Nov 12, 2007 at 05:26:24PM +0530, Amit Shah wrote:
On Monday 12 November 2007 16:20:01 Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to
On Mon, Nov 12, 2007 at 07:25:27PM +0530, Amit Shah wrote:
Selectively? What happens in the case when some iommu doesn't want
to invoke the prev_op, but the mapping depends on it being called
(eg, the hypercalling op is embedded somewhere in the prev_op chain)
Bad things :-)
There needs to be
Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to our structure so
that every DMA access goes through us. (This is the reason this only
works for 64-bit guest. 32-bit guest doesn't yet have a dma_ops
struct.)
On Mon, Nov 12, 2007 at 12:50:01PM +0200, Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to our structure so
that every DMA access goes through us. (This is the reason this only
works for 64-bit guest.
