On Mon, Feb 25, 2013 at 12:02 PM, H. Peter Anvin <hpa@xxxxxxxxx> wrote: > On 02/25/2013 12:00 PM, Yinghai Lu wrote: >> >> Can replace max_low_pfn_mapped with max_low_pfn instead ? >> like to see if you can put acpi tables above 4G for x86_64. >> >> if it does not work, you can use min(max_low_pfn<<PAGE_SHIFT, 0xffffffffUL) >> instead. >> > > This is part of why we really need to get rid of these stupid variables > one and for all. The only exception should perhaps be to mark the > HIGHMEM crossover point on HIGHMEM systems. yes, we can drop max_low_pfn_mapped at least. I should drop that in for-x86-mm2 time point, but saw ThomasR is using that, so i dropped that patch to make the merge easy. Now after Thomas change to max_low_pfn, we can drop max_low_pfn_mapped. Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
