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

WARNING - OLD ARCHIVES

http://lists.xen.org/

To:	"Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] Calling __va() in a x86_64 Dom0 module
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
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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
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 in Thread]

Current Thread

[Next in Thread>

Previous by Date:

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

Next by Date:

[Xen-devel] [PATCH 5/4] ioports: iopif.py missing from last patch, Jody Belka

Previous by Thread:

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

Next by Thread:

RE: [Xen-devel] allocating AGP aperture memory, Langsdorf, Mark

Indexes:

[Date] [Thread] [Top] [All Lists]