On Thu, 22 Jul 2010, Jack Steiner wrote: > Large SGI UV systems (3072p, 5TB) take a long time to boot. A significant > part of the boot time is scanning ACPI tables. ACPI tables on UV systems > are located in RAM memory that is physically attached to node 0. > > User programs (ex., acpidump) read the ACPI tables by mapping them thru > /dev/mem. Although mmap tries to map the tables as CACHED, there are > existing kernel UNCACHED mapping that conflict and the tables end up as > being mapped UNCACHED. (See the call to track_pfn_vma_new() in > remap_pfn_range()). Well, as it was raised in this thread, ACPI tables are likely to be near RAM regions used for IPC with the firmware or SMBIOS, and we have no idea of the kind of crap that could happen if we enable caching on those areas. OTOH, we *know* of systems that force us to copy the ACPI tables to regular RAM, otherwise, the utterly broken BIOS corrupts the ACPI tables after the kernel has loaded. Couldn't we simply always copy all tables to regular RAM and mark THAT as cacheable (since there will be no IPC regions in it)? For the tables that are only used once, we can free the RAM later. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
