Hello,
On Fri, Jul 19, 2013 at 03:59:28PM +0800, Tang Chen wrote:
> /*
> + * kernel_resides_in_range - Check if kernel resides in a memory range.
> + * @base: The base address of the memory range.
> + * @length: The length of the memory range.
> + *
> + * memblock reserves some memory for the kernel at very early time, such
> + * as kernel code and data segments, initrd file, and so on. So this
> + * function iterates memblock.reserved[] and check if any memory range with
> + * flag MEMBLK_FLAGS_DEFAULT overlaps [@base, @length). If so, the kernel
> + * resides in this memory range.
> + *
> + * Return true if the kernel resides in the memory range, false otherwise.
> + */
> +static bool __init kernel_resides_in_range(phys_addr_t base, u64 length)
> +{
> + int i;
> + struct memblock_type *reserved = &memblock.reserved;
> + struct memblock_region *region;
> + phys_addr_t start, end;
> +
> + for (i = 0; i < reserved->cnt; i++) {
> + region = &reserved->regions[i];
> +
> + if (region->flags != MEMBLK_FLAGS_DEFAULT)
> + continue;
> +
> + start = region->base;
> + end = region->base + region->size;
> + if (end <= base || start >= base + length)
> + continue;
> +
> + return true;
> + }
> +
> + return false;
> +}
This being in acpi/osl.c is rather weird. Overall, the acpi and
memblock parts don't seem very well split. It'd best if acpi just
indicates which regions are hotpluggable and the rest is handled by
x86 boot or memblock code as appropriate.
Thanks.
--
tejun
--
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
