* ykzhao <yakui.zhao@xxxxxxxxx> wrote: > From the above description maybe the E820_ACPI region can be mapped as > cached. But this still depends on the BIOS. If the some shared data resides > in the E820_ACPI region on some BIOS, maybe we can't map the E820_ACPI > region as cached again. I dont think we can do this safely unless some other OS (Windows) does it as well. (the reason is that if some BIOS messes this up then it will cause nasty bugs/problems only on Linux.) But the benefits of caching are very clear and well measured by Jack, so we want the feature. What we can do is to add an exception for 'known good' hw vendors - i.e. something quite close to Jack's RFC patch, but implemented a bit more cleanly: Exposing x86_platform and e820 details to generic ACPI code isnt particularly clean - there should be an ACPI accessor function for that or so: a new acpi_table_can_be_cached(table) function or so. In fact since __acpi_map_table(addr,size) is defined by architectures already, this could be done purely within x86 code. Thanks, Ingo -- 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
