From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Using mini-os ioremap() Date: Thu, 6 Jan 2011 18:19:21 +0100 Message-ID: <20110106171921.GF5776@const.bordeaux.inria.fr> References: <4D24C587.6060907@jhuapl.edu> <20110105225552.GI4618@const.famille.thibault.fr> <4D25F514.3010502@jhuapl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4D25F514.3010502@jhuapl.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Matthew Fioravante Cc: Rolf Neugebauer , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Matthew Fioravante, le Thu 06 Jan 2011 12:00:04 -0500, a =E9crit : > My box doesn't have more than 4GB. I've tried this on 32 bit and 64 bi= t. How much does it have? Could you post the memory map recorded in xm dmesg? > I tried nuking the mfn_is_ram check. When I do that the call returns a=20 > virtual memory address but when I try to read and write to it, it=20 > appears to act just like a normal page of memory and not the device. Mmm... I wonder how that can be possible if your address is really an IO area. > Does anyone know offhand of a mini-os project that either tested the=20 > ioremap() call or actually does some memory mapped io operations? It was implemeted by Rolf Neugebauer , Cc-ed. Samuel