From: Matthew Fioravante <matthew.fioravante@jhuapl.edu>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Using mini-os ioremap()
Date: Thu, 06 Jan 2011 12:00:04 -0500 [thread overview]
Message-ID: <4D25F514.3010502@jhuapl.edu> (raw)
In-Reply-To: <20110105225552.GI4618@const.famille.thibault.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1482 bytes --]
My box doesn't have more than 4GB. I've tried this on 32 bit and 64 bit.
I tried nuking the mfn_is_ram check. When I do that the call returns a
virtual memory address but when I try to read and write to it, it
appears to act just like a normal page of memory and not the device.
Does anyone know offhand of a mini-os project that either tested the
ioremap() call or actually does some memory mapped io operations?
On 01/05/2011 05:55 PM, Samuel Thibault wrote:
> Matthew Fioravante, le Wed 05 Jan 2011 14:24:55 -0500, a écrit :
>> I'm trying to map some mmio pages into my mini-os domain to use a
>> hardware device. The device is at address fed40000. I'm calling
>> ioremap() on this address but its failing, telling me that mfn fed40 is
>> in ram space. (Its failing the mfn_is_ram() check.)
>>
>> What am I doing wrong here?
> Mmm, I don't think anything you're doing is wrong. Notice the comment:
>
> static long system_ram_end_mfn;
> int mfn_is_ram(unsigned long mfn)
> {
> /* very crude check if a given MFN is memory or not. Probably should
> * make this a little more sophisticated ;) */
> return (mfn<= system_ram_end_mfn) ? 1 : 0;
> }
>
> Do you have more than 4GiB memory, i.e. 0xfed40000 is actually between
> two RAM areas? In such case mfn_is_ram has to really get more
> sophisticated.
>
> (In the interim you could just comment the mfn_is_ram() test from
> do_ioremap to make things work)
>
> Samuel
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2518 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-01-06 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 19:24 Using mini-os ioremap() Matthew Fioravante
2011-01-05 22:55 ` Samuel Thibault
2011-01-06 17:00 ` Matthew Fioravante [this message]
2011-01-06 17:19 ` Samuel Thibault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D25F514.3010502@jhuapl.edu \
--to=matthew.fioravante@jhuapl.edu \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).