From: Dan Malek <dan@netx4.com>
To: zzh <david-1z@263.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: memory map
Date: Fri, 21 Apr 2000 12:58:28 -0400 [thread overview]
Message-ID: <390088B4.5408B5EF@embeddededge.com> (raw)
In-Reply-To: 39002421.07687@mta1
zzh wrote:
> 1)Some area eg BCSR mapped below KERNELBASE,is this safe?
If you ioremap() after the kernel VM allocator is initialized, this
is fine. You then get a kernel virtual address to use that will
map to the physical address. Don't map this in mm/init.c initialization
as this maps 1:1 because the VM is not initialized yet. The things
mapped in mm/init.c should be just the minimum to debug or get
the kernel booted.
> I check some process's vm area,it does not fall in this area,will
> it be unsafe under some circumstances?
The "some" circumstances are incorrect mapping during the early
initialization.
> 2)I read mapin_ram() in mm/init.c ,found that phys mem is also mapped
> both by bat and page table ,what is this for?
Physical memory is mapped by BATs, if they exist on the processor.
Since the 8xx doesn't have BATs, the memory is mapped through page
tables.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-21 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 9:49 memory map zzh
2000-04-21 16:58 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-24 3:24 zzh
2000-04-24 3:54 ` Dan Malek
2000-04-23 22:16 ` Steve Tarr
2000-04-24 16:07 ` Dan Malek
2000-04-24 5:11 Shuangjun Zhu
2000-04-24 16:09 ` Dan Malek
2000-04-25 9:31 zzh
2000-04-25 17:05 ` Dan Malek
2000-11-27 19:04 Memory map Konstantin Sabodash
2000-11-27 19:22 ` Dan Malek
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=390088B4.5408B5EF@embeddededge.com \
--to=dan@netx4.com \
--cc=david-1z@263.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).