[PATCH 0/8] ACPI: Fixes and cleanups related to iomaps management (v2)

[Rafael J. Wysocki]

Hi Len,

The following series of patches implements some fixes of the ACPI iomaps
management.  I found the problems trying to resolve the issue of creating
iomaps of regions that have been mapped already when we save the NVS region.

To me, they are not extremely urgent, because the related issues are generally
long-standing, but some bugs addressed by them (especially [1/9]) may be
actively hurting people right now, so they look suitable for .38 as well.
This is your call, though.
 
[1/8] - Fix routines for reading and writing iomem (RCU bug; new version of the
        patch).

[2/8] - (cleanup) Do not export local functions in osl.c (this one is the same
        as https://patchwork.kernel.org/patch/491551/).

[3/8] - Use a mutex (instead of a spinlock) for the locking of iomap
        manipulations in osl.c (same as
        https://patchwork.kernel.org/patch/491751/).

[4/8] - Avoid unnecessary walks of the list of iomaps in osl.c (same as
        https://patchwork.kernel.org/patch/491671/).

[5/8] - Avoid creating iomaps for regions that have been mapped already (same
         as https://patchwork.kernel.org/patch/491741/).

[6/8] - Replace krefs used for iomap refcounting with simple reference
        counters (they are manipulated under a lock anyway; same as
        https://patchwork.kernel.org/patch/491681/).

[7/8] - Introduce function for getting a reference to an ACPI iomap (to be
        used by the NVS save/restore code; same as
        https://patchwork.kernel.org/patch/491701/).

[8/8] - Make the NVS code use existing iomaps if possible (new version).

The patches have been tested on HP nx6325, Toshiba Portege R500 and Acer
Ferrari One without causing any visible problems to happen.
 
Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/