On 02/07/2010 12:50 PM, Joerg Roedel wrote:
On Sun, Feb 07, 2010 at 11:38:30AM +0200, Avi Kivity wrote:
On 01/28/2010 01:37 PM, Joerg Roedel wrote:
These two functions provide support for mapping and
unmapping physical addresses to io virtual addresses. The
difference to the iommu_(un
On Sun, Feb 07, 2010 at 11:38:30AM +0200, Avi Kivity wrote:
> On 01/28/2010 01:37 PM, Joerg Roedel wrote:
>> These two functions provide support for mapping and
>> unmapping physical addresses to io virtual addresses. The
>> difference to the iommu_(un)map_range() is that the new
>> functions take
On 01/28/2010 01:37 PM, Joerg Roedel wrote:
These two functions provide support for mapping and
unmapping physical addresses to io virtual addresses. The
difference to the iommu_(un)map_range() is that the new
functions take a gfp_order parameter instead of a size. This
allows the IOMMU backend i
These two functions provide support for mapping and
unmapping physical addresses to io virtual addresses. The
difference to the iommu_(un)map_range() is that the new
functions take a gfp_order parameter instead of a size. This
allows the IOMMU backend implementations to detect easier if
a given ran