linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@linuxcare.com.au>
To: Tilmann Bitterberg <tibit-ibm@bitterberg.de>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: HIGHMEM now working
Date: Tue, 17 Oct 2000 15:52:41 +1100 (EST)	[thread overview]
Message-ID: <14827.56089.260884.298273@argo.linuxcare.com.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0010161220230.1783-200000@karl.rchland.ibm.com>


Tilmann Bitterberg writes:

> I saw that you recently did some fixes for HIGHMEM on CHRP, but
> they did not work. Actually, I can't get the kernel to boot on a

Where did you get the version you tried?  I recently got a kernel
going with highmem on a 44p/170 but I haven't pushed all the changes
into bk.  I had to make several changes to the python code as well as
arch/ppc/mm/init.c and my changes are somewhat different to what is
being done in the linuxppc_2_5 tree.  My changes are available in the
rsync tree at ppc.samba.org::linux-pmac-devel but that is
unfortunately almost unusable because of bandwidth restrictions on
that machine.  I am trying to get a ppc.linuxcare.com machine set up
in California but that is proving to be a slow process.

> Why not just lower PKMAP_BASE to 0xf6000000, will this break
> someone?

Everyone, potentially. :-)  You're lucky it worked.

The way the code is at the moment, we divide up the space between the
end of RAM and the end of the address space (0xffffffff) like this:

    end of RAM ... end of RAM + VMALLOC_OFFSET:	    not used
    end of RAM + VMALLOC_OFFSET ... ioremap_bot:    vmalloc & ioremap
    ioremap_bot ... ioremap_base:		    early ioremaps
    ioremap_base ... 0xffffffff:		    ioremap virt = phys

In other words all of the address space from end of RAM +
VMALLOC_OFFSET is potentially used by ioremap (which is a bit greedy
of it really).  I personally think that the code in ioremap which
assigns virt = phys for phys >= ioremap_base should go away.  For now
I have added an extra check in the highmem case so that it only uses
virt = phys for ioremap_base <= phys <= PKMAP_BASE.  This shows up one
or two missing ioremaps in the chrp code which I have fixed in my
version.

Paul.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-10-17  4:52 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 [this message]
2000-10-17  5:17   ` Dan Malek
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=14827.56089.260884.298273@argo.linuxcare.com.au \
    --to=paulus@linuxcare.com.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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).