Andy, We are about to release new table code, which will not allocate memory for any tables, but just map them from their physical location, does it solve the problem you describe? Regards, Alex. Andi Kleen wrote: > [repost, this time with correct cc list] > > AFAIK ACPI saves all information found in ACPI tables in memory > somewhere else (please correct me if I'm wrong on that) > > I also found this comment in e820.h: > > #define E820_ACPI 3 /* usable as RAM once ACPI tables have been read */ > > Currently I don't see any code that would free the ACPI tables after they > are read. During SLES10 testing we had some problems with the ACPI > tables on some Unisys systems being in a area where the kexec kernel > wanted to be loaded too. Also on other systems the ACPI tables are not > exactly at the end but in the middle of the memory map and for some applications > it might be better to have a lot of physical continuous memory. > > So are there any plans to free the BIOS supplied ACPI tables after parsing > or is there some obstacle to that that I'm missing? > > Thanks, > -Andi > > - > 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 > - 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
