[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [kvm-devel] [Qemu-devel] [PATCH 2/6] PCI DMA API (v2)
From: |
andrzej zaborowski |
Subject: |
Re: [kvm-devel] [Qemu-devel] [PATCH 2/6] PCI DMA API (v2) |
Date: |
Sun, 6 Apr 2008 19:01:09 +0200 |
On 06/04/2008, Anthony Liguori <address@hidden> wrote:
> Blue Swirl wrote:
> > To support Sparc IOMMU and DMA controller
> > I need a way to call a series of different translation functions
> > depending on the bus where we are. For the byte swapping case the
> > memcpy functions must be dynamic as well.
>
> Does DMA really byte-swap? I know PCI controllers byte swap within the
> configuration space but I didn't think they byte-swapped DMA transfers. I'm
> not even sure how that would work.
As a note, the DMA controllers in the ARM system-on-chip's can
byte-swap, do 90deg rotation of 2D arrays, transparency (probably
intened for image blitting, but still available on any kind of
transfers), etc., and most importantly issue interrupts on reaching
different points of a transfer. It is not worth worrying about them
in this API. I have been for some time wanting to make a separate api
called soc_dma whose task would be using simply memcpy (or zero-copy)
in the most basic case (interrupts off, no transparency,
same-endianness endpoints), as these properties are common for DMA on
the TI OMAPs, the Intel PXAs and the Samsung S3Cs (which otherwise
have little in common).
Cheers
--
Please do not print this email unless absolutely necessary. Spread
environmental awareness.
Re: [Qemu-devel] [PATCH 2/6] PCI DMA API (v2), Paul Brook, 2008/04/07
Re: [Qemu-devel] [PATCH 1/6] Use ram_addr_t for cpu_get_physical_page_desc (v2), Paul Brook, 2008/04/06