pte_offset_map for ppc assumes HIGHPTE
schwab at suse.de
Thu Jul 26 09:18:48 EST 2007
Satya <satyakiran at gmail.com> writes:
> The implementation of pte_offset_map() for ppc assumes that PTEs are
> kept in highmem (CONFIG_HIGHPTE). There is only one implmentation of
> pte_offset_map() as follows (include/asm-ppc/pgtable.h):
> #define pte_offset_map(dir, addr) \
> ((pte_t *) kmap_atomic(pmd_page(*(dir)), KM_PTE0) + pte_index(addr))
> Shouldn't this be made conditional according to CONFIG_HIGHPTE is
> defined or not
kmap_atomic is always defined with or without CONFIG_HIGHPTE.
> (as implemented in include/asm-i386/pgtable.h) ?
I don't think that needs it either.
Andreas Schwab, SuSE Labs, schwab at suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Linuxppc-dev