[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Calling __va() in a x86_64 Dom0 module

To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 6 Nov 2005 19:38:47 -0000
Cc: "Forsgren, Garry" <Garry.Forsgren@xxxxxxxxxx>
Delivery-date: Sun, 06 Nov 2005 19:39:09 +0000
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcXfJauwtSpYwRXYQc+ukrtR/C5nVwDO3mSwACdQ7gAAArsY4A==
Thread-topic: [Xen-devel] Calling __va() in a x86_64 Dom0 module

> I was able to use ioremap() to gain access to the piece of 
> memory. Is this a reliable method or should I be using 
> direct_remap_pfn_range()?

direct_remap_pfn_range is called by ioremap -- you're indeed correct to
be using the latter.

Best,
Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Prev by Date: RE: [Xen-devel] Calling __va() in a x86_64 Dom0 module
Next by Date: [Xen-devel] [PATCH 5/4] ioports: iopif.py missing from last patch
Previous by thread: RE: [Xen-devel] Calling __va() in a x86_64 Dom0 module
Next by thread: RE: [Xen-devel] allocating AGP aperture memory
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.