From: Russell King <rmk@arm.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-mm@kvack.org,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] pae-2.4.3-A4
Date: Sun, 25 Mar 2001 17:33:44 +0100 [thread overview]
Message-ID: <20010325173344.B30655@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.31.0103191839510.1003-100000@penguin.transmeta.com> <Pine.LNX.4.30.0103251643070.6469-200000@elte.hu>
In-Reply-To: <Pine.LNX.4.30.0103251643070.6469-200000@elte.hu>; from mingo@elte.hu on Sun, Mar 25, 2001 at 04:53:37PM +0200
On Sun, Mar 25, 2001 at 04:53:37PM +0200, Ingo Molnar wrote:
> one nontrivial issue was that on PAE the pgd has to be installed with
> 'present' pgd entries, due to a CPU erratum. This means that the
> pgd_present() code in mm/memory.c, while correct theoretically, doesnt
> work with PAE. An equivalent solution is to use !pgd_none(), which also
> works with the PAE workaround.
Certainly that's the way the original *_alloc routines used to work.
In fact, ARM never had need to implement the pmd_present() macros, since
they were never referenced - only the pmd_none() macros were.
However, I'm currently struggling with this change on ARM - so far after
a number of hours trying to kick something into shape, I've not managed
to even get to the stange where I get a kernel image to link, let alone
the compilation to finish.
One of my many dilemas at the moment is how to allocate the page 0 PMD
in pgd_alloc(), where we don't have a mm_struct to do the locking against.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-25 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0103191802330.2076-100000@mikeg.weiden.de>
2001-03-20 1:56 ` 3rd version of R/W mmap_sem patch available Rik van Riel
2001-03-19 22:46 ` Linus Torvalds
2001-03-20 2:46 ` Linus Torvalds
2001-03-20 4:15 ` Marcelo Tosatti
2001-03-20 6:07 ` Linus Torvalds
2001-03-20 4:29 ` Marcelo Tosatti
2001-03-20 6:36 ` Linus Torvalds
2001-03-21 18:12 ` 2.4.3-pre6 alpha pte/pmd_alloc update Ivan Kokshaysky
2001-03-25 14:53 ` [patch] pae-2.4.3-A4 Ingo Molnar
2001-03-25 16:33 ` Russell King [this message]
2001-03-25 18:07 ` Linus Torvalds
2001-03-25 18:51 ` Ingo Molnar
2001-03-30 14:01 ` [PATCH] PAE zap_low_mappings no-op Hugh Dickins
2001-04-09 16:01 ` [PATCH] 2.4.4-pre1 sparc/mm typo Hugh Dickins
2001-03-26 8:45 [patch] pae-2.4.3-A4 Studierende der Universitaet des Saarlandes
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=20010325173344.B30655@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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