pte_update and 64-bit PTEs on PPC32?
benh at kernel.crashing.org
Wed Apr 6 16:53:38 EST 2005
On Wed, 2005-04-06 at 01:51 -0500, Kumar Gala wrote:
> I've tracked down a bug I've been having to the fact that pte_update
> assumes a pte is a unsigned long. I need to look into what the exact
> implications this has. I was wondering what the thoughts were with
> respect to how this is suppose to work properly on 440 with its 64-bit
> pte? I'm looking at a 64-bit pte for some Freescale book-e parts as we
> move to 36-bit physical address support.
> The problem I found was ptep_get_and_clear() would return back only a
> 32-bit value and thus we loose any information in the upper 32-bits. I
> found the call in sys_mprotect ... -> change_pte_range ->
> Will provide some update on this tomorrow.
It's quite important for the flags to all be together in a single 32
bits entity so that atomic operations can be done on them. The RPN
should be able to extend beyond the initial 32 bits provided we are
careful about the way we manipulate the PTEs. When setting a PTE, we
should always first set the "other" part, then the PTE present bit last
or a CPU would possibly get a stale PTE. The problem with that scheme is
that I can see possible races on dual page faults trying to fill in the
same PTE if we drop the page table lock (christoph lameter stuff) but it
should work for us now.
More information about the Linuxppc-embedded