http://bugzilla.kernel.org/show_bug.cgi?id=14445
--- Comment #3 from Robert Moore <[email protected]> 2009-10-20 22:16:55 --- Looking at the code, it looks to me that when creating a mapping, the length it uses is the smaller of: 1) The end of the operation region minus the requested address, and 2) ACPI_SYSMEM_REGION_WINDOW_SIZE Therefore, the code is not blindly just mapping ACPI_SYSMEM_REGION_WINDOW_SIZE; it is only mapping (at most) to the end of the operation region. So, page boundaries should have no bearing on the problem; the code will only map to the end of the operation region and presumably sooner or later a mapping will be created that conflicts (assuming that the definition of the region actually intrudes into a page that is used for something else.) Below, MemInfo->Address is the base physical address of the region MemInfo->Length is the length of the region Address is the requested physical address /* * Don't attempt to map memory beyond the end of the region, and * constrain the maximum mapping size to something reasonable. */ WindowSize = (ACPI_SIZE) ((MemInfo->Address + MemInfo->Length) - Address); if (WindowSize > ACPI_SYSMEM_REGION_WINDOW_SIZE) { WindowSize = ACPI_SYSMEM_REGION_WINDOW_SIZE; } -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
