This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Physical address mapping to user space in dom0 problem

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Physical address mapping to user space in dom0 problem
From: "Haw-Yuan Yang" <hawyuan@xxxxxxxxx>
Date: Fri, 16 Mar 2007 16:27:07 -0700
Delivery-date: Fri, 16 Mar 2007 16:26:05 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=oEodMPmypxNiKe3lPNPuWxxg/CaTjy1+NTbo7UYCHBLC/Kj4XQ/yAOfHlxBTSxUD60b5jqKmkuwZfFxh4Mh3xHH+OAwMoZuBo0ZLBGdaWJMiNX4LKr1WtiWnCWgVg1jmwLkFtS7n0JlM3Stt3m6YCddh2XozeU4O35fGw8YmJXA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=N+kwRCW4wnQMbl66ZStG2ZxD1aN8z1x3KZCHP90KT//R+GkRRkldbfo1jUVYAbiTeI7t5gKWhiavPMrp50GX3gNC+3jogW+Zj6k849FaqclV/fNs7H9EwPF6fxu72cvgfHe9kzQnDu9UMxUyvF4GfJ+yMliY34wKAMSaAfmWtbE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I have a PCI device which can perform bus master DMA. I developed a PCI device driver which can allocate DMA buffer and provide mmap operation to map the I/O and DMA buffer to user space.


The PCI device driver works well under Linux 2.6.20. However it brokes under XEN 3.0.4. It appears that mmap map to the wrong memory.  remap_pfn_range in mmap function return no error when it is used to map both I/O and DMA buffer.  If I use io_remap_pfn_range instead of   remap_pfn_range, I/O mapping works but DMA buffer mapping return -1.


Is this a known problem for XEN 3.0.4 and will be fixed later? Is there any alternative way to map the DMA address to user space in XEN dom0?


Thanks in advance,



Xen-devel mailing list