From: Pratyush Anand <panand@redhat.com>
To: Baoquan He <bhe@redhat.com>,
"AKASHI, Takahiro" <takahiro.akashi@linaro.org>
Cc: kexec@lists.infradead.org, kexec@lists.fedoraproject.org
Subject: Re: [PATCH RFC 3/6] arm64: allocate memory for other segments after kernel
Date: Tue, 21 Apr 2015 09:49:18 +0530 [thread overview]
Message-ID: <5535CFC6.4010802@redhat.com> (raw)
In-Reply-To: <20150420032106.GF15033@dhcp-16-116.nay.redhat.com>
On Monday 20 April 2015 08:51 AM, Baoquan He wrote:
> On 04/16/15 at 10:17pm, Pratyush Anand wrote:
>> In case of KEXEC_ON_CRASH, load other segments after the addresses where
>> kernel segments finish.
>>
>> Signed-off-by: Pratyush Anand <panand@redhat.com>
>> ---
>> kexec/arch/arm64/crashdump-arm64.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/kexec/arch/arm64/crashdump-arm64.c b/kexec/arch/arm64/crashdump-arm64.c
>> index 41266f294589..75f4e4d269ca 100644
>> --- a/kexec/arch/arm64/crashdump-arm64.c
>> +++ b/kexec/arch/arm64/crashdump-arm64.c
>> @@ -312,5 +312,6 @@ void set_crash_entry(struct mem_ehdr *ehdr, struct kexec_info *info)
>> off_t locate_dtb_in_crashmem(struct kexec_info *info, off_t dtb_size)
>> {
>> return locate_hole(info, dtb_size, 128UL * 1024,
>> - crash_reserved_mem.start, crash_reserved_mem.end, 1);
>> + crash_reserved_mem.start + arm64_mem.text_offset +
>> + arm64_mem.image_size, crash_reserved_mem.end, 1);
>
> So you have decided to hard code the sequence of segment. It
> seems not good. Why don't do it by calling add_buffer_phys_virt() or
> implement a similar function if you don't like add_buffer_phys_virt.
I agree that code is a bit tightly coupled here. I think, Takahiro can
comment better.
arm64 does use add_buffer_phys_virt to add all the buffers into segment
list. arm64_load_other_segments function adds buffers for all segments
other than kernel and elfcorehdr. This function calls
add_buffer_phys_virt to load different segments like dtb, initrd and
purgatory. Only limitation we are putting that we find free area for all
these segments after the area where kernel finishes. Currently load
sequence is like dtb, initrd and then purgatory. But I believe, even if
we use other load sequence in arm64_load_other_segments, it should work.
Not sure, if understood the question and replied well.
~Pratyush
>
>> }
>> --
>> 2.1.0
>>
>>
>> _______________________________________________
>> kexec mailing list
>> kexec@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-04-21 4:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 16:47 [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 1/6] purgatory: Fix memcmp for src address increment Pratyush Anand
2015-04-17 16:55 ` Geoff Levand
2015-04-20 0:25 ` Simon Horman
2015-04-22 11:19 ` Pratyush Anand
2015-04-23 2:23 ` Simon Horman
2015-04-16 16:47 ` [PATCH RFC 2/6] purgatory: No need to sha256 update if ptr->len is zero Pratyush Anand
2015-04-17 16:58 ` Geoff Levand
2015-04-17 23:26 ` Pratyush Anand
2015-04-20 3:01 ` Baoquan He
2015-04-20 3:18 ` Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 3/6] arm64: allocate memory for other segments after kernel Pratyush Anand
2015-04-17 16:59 ` Geoff Levand
2015-04-20 3:21 ` Baoquan He
2015-04-21 4:19 ` Pratyush Anand [this message]
2015-04-21 10:06 ` AKASHI Takahiro
2015-04-22 6:16 ` AKASHI Takahiro
2015-04-16 16:47 ` [PATCH RFC 4/6] arm64: support reuse-cmdline option Pratyush Anand
2015-04-17 17:02 ` Geoff Levand
2015-04-16 16:47 ` [PATCH RFC 5/6] arm64: Add support for binary image Pratyush Anand
2015-04-17 17:07 ` Geoff Levand
2015-04-17 18:00 ` Geoff Levand
2015-04-17 23:27 ` Pratyush Anand
2015-04-20 7:24 ` Baoquan He
2015-04-21 4:42 ` Pratyush Anand
2015-04-22 2:53 ` Baoquan He
2015-04-22 11:19 ` Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 6/6] arm64: wait for transmit completion before next character transmission Pratyush Anand
2015-04-17 5:36 ` Minfei Huang
2015-04-17 5:37 ` Pratyush Anand
2015-04-20 2:58 ` Baoquan He
2015-04-20 3:34 ` Pratyush Anand
2015-04-17 17:22 ` Geoff Levand
2015-04-17 23:31 ` Pratyush Anand
2015-04-16 23:54 ` [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Simon Horman
2015-04-17 1:27 ` Dave Young
2015-04-17 2:48 ` Pratyush Anand
2015-04-17 17:27 ` Geoff Levand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5535CFC6.4010802@redhat.com \
--to=panand@redhat.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.fedoraproject.org \
--cc=kexec@lists.infradead.org \
--cc=takahiro.akashi@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox