Re: [PATCH v8 14/46] x86, mm: use pfn_range_is_mapped() with reserve_initrd

[Yinghai Lu]

On Wed, Nov 28, 2012 at 9:08 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Fri, Nov 16, 2012 at 07:38:51PM -0800, Yinghai Lu wrote:
>> We are going to map ram only, so under max_low_pfn_mapped,
>> between 4g and max_pfn_mapped does not mean mapped at all.
>>
>> Use pfn_range_is_mapped() to find out if range is mapped for initrd.
>>
>> That could happen bootloader put initrd in range but user could
>                    ^- 'if the'                              ^^^^^-'used'
>
>> use memmap to carve some of range out.
>   ^^^-> get rid of that.       ^^^^->'ranges'
>
>>
>> Also during copying need to use early_memmap to map original initrd
>> for accessing.

===>
---
We are going to map ram only in patch:
        x86, mm: Only direct map addresses that are marked as E820_RAM

so range under max_low_pfn_mapped, ranges between 4g and max_pfn_mapped
could have holes in them and the holes will not be mapped.

Use pfn_range_is_mapped() to check if range is mapped for initrd.

That could happen if the bootloader put initrd in range but user used
"memmap=" to carve some of ranges out.

Also during copying need to use early_memmap to map original initrd
for accessing.
---
--
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/