Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761304AbZCMRJ2 (ORCPT ); Fri, 13 Mar 2009 13:09:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760047AbZCMRBx (ORCPT ); Fri, 13 Mar 2009 13:01:53 -0400 Received: from gw.goop.org ([64.81.55.164]:57424 "EHLO abulafia.goop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759677AbZCMRBw (ORCPT ); Fri, 13 Mar 2009 13:01:52 -0400 From: Jeremy Fitzhardinge To: "H. Peter Anvin" Cc: the arch/x86 maintainers , Linux Kernel Mailing List , Xen-devel , David Airlie , Jeremy Fitzhardinge Subject: [PATCH 18/27] xen/swiotlb: add sync functions Date: Fri, 13 Mar 2009 10:00:03 -0700 Message-Id: <1236963612-14287-19-git-send-email-jeremy@goop.org> X-Mailer: git-send-email 1.6.0.6 In-Reply-To: <1236963612-14287-1-git-send-email-jeremy@goop.org> References: <1236963612-14287-1-git-send-email-jeremy@goop.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1242 Lines: 36 From: Jeremy Fitzhardinge Add all the missing sync functions. This fixes iwlagn. (Need to think about what to do with non-swiotlb mode.) Signed-off-by: Jeremy Fitzhardinge --- drivers/pci/xen-iommu.c | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/drivers/pci/xen-iommu.c b/drivers/pci/xen-iommu.c index 13cfe0c..afcebf9 100644 --- a/drivers/pci/xen-iommu.c +++ b/drivers/pci/xen-iommu.c @@ -303,6 +303,13 @@ static struct dma_map_ops xen_swiotlb_dma_ops = { .mapping_error = swiotlb_dma_mapping_error, + .sync_single_for_cpu = swiotlb_sync_single_for_cpu, + .sync_single_for_device = swiotlb_sync_single_for_device, + .sync_single_range_for_cpu = swiotlb_sync_single_range_for_cpu, + .sync_single_range_for_device = swiotlb_sync_single_range_for_device, + .sync_sg_for_cpu = swiotlb_sync_sg_for_cpu, + .sync_sg_for_device = swiotlb_sync_sg_for_device, + .is_phys = 0, }; -- 1.6.0.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/