Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map

From	yalin wang <yalin.wang2010@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map
Date	2015-10-08 11:20 +0200
Message-ID	<qhfwJ-7zW-13@gated-at.bofh.it> (permalink)
References	(1 earlier) <pYw53-5aC-3@gated-at.bofh.it> <q6ppL-2YE-3@gated-at.bofh.it> <qgE49-49R-11@gated-at.bofh.it> <qgE49-49R-17@gated-at.bofh.it> <qhf3J-6MG-17@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> On Oct 8, 2015, at 16:49, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> 
> On Tue, Oct 06, 2015 at 01:16:52PM -0400, Mark Salter wrote:
>> On Tue, 2015-10-06 at 18:11 +0100, Mark Rutland wrote:
>>> On Tue, Sep 08, 2015 at 12:31:13PM +0100, Mark Rutland wrote:
>>>> Hi Mark,
>>>> 
>>>> On Mon, Aug 17, 2015 at 06:01:06PM +0100, Mark Salter wrote:
>>>>> The use of mem= could leave part or all of the initrd outside of
>>>>> the kernel linear map. This will lead to an error when unpacking
>>>>> the initrd and a probable failure to boot. This patch catches that
>>>>> situation and relocates the initrd to be fully within the linear
>>>>> map.
>>>> 
>>>> With next-20150908, this patch results in a confusing message at boot when not
>>>> using an initrd:
>>>> 
>>>> Moving initrd from [4080000000-407fffffff] to [9fff49000-9fff48fff]
>>>> 
>>>> I think that can be solved by folding in the diff below.
>>> 
>>> Mark, it looks like this fell by the wayside.
>>> 
>>> Do you have any objection to this? I'll promote this to it's own patch
>>> if not.
>>> 
>>> Mark.
>>> 
>>>> 
>>>> Thanks,
>>>> Mark.
>>>> 
>>>> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
>>>> index 6bab21f..2322479 100644
>>>> --- a/arch/arm64/kernel/setup.c
>>>> +++ b/arch/arm64/kernel/setup.c
>>>> @@ -364,6 +364,8 @@ static void __init relocate_initrd(void)
>>>>                to_free = ram_end - orig_start;
>>>> 
>>>>        size = orig_end - orig_start;
>>>> +       if (!size)
>>>> +               return;
>>>> 
>>>>        /* initrd needs to be relocated completely inside linear mapping */
>>>>        new_start = memblock_find_in_range(0, PFN_PHYS(max_pfn),
>> 
>> Sorry, no. That looks perfectly good to me.
>> 
is it also possible to implement it on ARM platforms?
ARM64 platform don’t have HIGH_MEM zone .
but ARM platform have .
i remember boot loader must put init rd  into low memory region,
so if some boot loader put init rd into HIGH men zone
we can also relocate it to low men region ?
then boot loader don’t need care about this ,
and since vmalloc= boot option will change HIGH mem region size,
if we can relocate init rd , boot loader don’t need care about init rd load address,
when change vmalloc= boot options .


Thanks









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

Thread

Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map Mark Rutland <mark.rutland@arm.com> - 2015-10-06 19:20 +0200
  Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map Mark Salter <msalter@redhat.com> - 2015-10-06 19:20 +0200
    Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map Christoffer Dall <christoffer.dall@linaro.org> - 2015-10-08 10:50 +0200
      Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map yalin wang <yalin.wang2010@gmail.com> - 2015-10-08 11:20 +0200
        Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map Russell King - ARM Linux <linux@arm.linux.org.uk> - 2015-10-08 11:50 +0200

csiph-web