It looks like the existing pfn_valid() returns bogus values on platforms where memory doesn't start at 0x0 (which is essentially all ia64 platforms as even those with memory at 0x0 usually can't use it because of cacheing issues with providing a WB mapping for the VGA mem at 0xc0000). -# define pfn_valid(pfn) (((pfn) < max_low_pfn) && ia64_pfn_valid(pfn)) +# define pfn_valid(pfn) (((pfn) >= min_low_pfn) && ((pfn) < max_low_pfn) && ia64_pfn_valid(pfn)) There's another pfn_valid() definition a few lines earlier in this file for the CONFIG_FLATMEM case. Does it need this treatment too? I'd guess not as Altix is far from flat. Yet another pfn_valid() in linux/mmzone.h (for CONFIG_SPARSEMEM). That one does table lookups ... presumably also safe. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Nov 10 10:24:38 2005
This archive was generated by hypermail 2.1.8 : 2005-11-10 10:24:56 EST