From: Dan Malek <dan@mvista.com>
To: paulus@linuxcare.com.au
Cc: Tilmann Bitterberg <tibit-ibm@bitterberg.de>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: HIGHMEM now working
Date: Tue, 17 Oct 2000 01:17:27 -0400 [thread overview]
Message-ID: <39EBE0E7.B9313EEE@mvista.com> (raw)
In-Reply-To: 14827.56089.260884.298273@argo.linuxcare.com.au
Paul Mackerras wrote:
> .... I personally think that the code in ioremap which
> assigns virt = phys for phys >= ioremap_base should go away.
Right, but that is just the most recent implementation for something
we have to admit exists and we integrate into your HIGHMEM and other
changes. We have to allow, somehow, mapping of board control registers
or other resources that must be used prior to page tables or other
VM initialization. Right now we map things in BATs or large TLB
entries and then use the code above (or some other variation) to
ensure the mapping sticks throughout the kernel lifetime. I don't
think it has to be virt == phys (which is just convenient for assembly
set up), but the mapping has to remain consistent even after the kernel
VM has been initialized. The reason virt == phys is convenient is
because we often access this space with and without the MMU enabled.
We would have to add some code in the places this is done to further
convert addresses, when right now we just write the functions without
any MMU assumptions.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-17 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-16 21:13 HIGHMEM now working Tilmann Bitterberg
2000-10-17 4:52 ` Paul Mackerras
2000-10-17 5:17 ` Dan Malek [this message]
2000-10-18 5:36 ` Paul Mackerras
2000-10-18 6:11 ` Dan Malek
2000-10-18 7:27 ` Wolfgang Denk
2000-10-18 15:41 ` Dan Malek
2000-10-17 15:05 ` Tilmann Bitterberg
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=39EBE0E7.B9313EEE@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
--cc=tibit-ibm@bitterberg.de \
/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).