From: Pratyush Anand <panand@redhat.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Geoff Levand <geoff@infradead.org>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH RFC 0/3] arm64: disable/enable d-cache support for
Date: Thu, 07 May 2015 10:24:15 +0530 [thread overview]
Message-ID: <554AEFF7.5070300@redhat.com> (raw)
In-Reply-To: <554AE924.4040208@linaro.org>
On Thursday 07 May 2015 09:55 AM, AKASHI Takahiro wrote:
> Geoff, Pratyush
>
> On 05/07/2015 02:37 AM, Pratyush Anand wrote:
>> Hi Geoff,
>>
>> On Wednesday 06 May 2015 10:35 PM, Geoff Levand wrote:
>>> Your 2 minutes seems like a long time. Is this seen on other platforms?
>>
>> At least it is seen on two different HW platforms I had tested with. I
>> do not know about other.
>>
>> It would be nice if somebody else who is using kexec on HW platform
>> can report their execution time.
>
> On my HW, it took about 42secs before showing extra boot messages after
> "I'm in purgatory."
>
It would also depend on the size of different segments (mainly kernel
and initrd) on which sha256 is calculated. What are the size of binaries
in your case?
In my case:
segment[0].memsz = 0x10e0000 // kernel
segment[1].memsz = 0x1910000 // initrd
segment[2].memsz = 0x10000 // dtb
segment[3].memsz = 0x40000 // purgatory, not included in sha256
segment[4].memsz = 0x10000 // elf core hdr
@Geoff: Do you see any specific side effect for enabling D-cache in
purgatory, other than the fact that it increases size of purgatory? May
be we can keep an user option to select/not select d-cache enabling.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-05-07 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 13:02 [PATCH RFC 0/3] arm64: disable/enable d-cache support for Pratyush Anand
2015-05-04 13:02 ` [PATCH RFC 1/3] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2015-05-04 13:02 ` [PATCH RFC 2/3] arm64: Pass RAM boundary to purgatory Pratyush Anand
2015-05-04 13:02 ` [PATCH RFC 3/3] arm64: Enable/disable D-cache before/after sha verification Pratyush Anand
2015-05-04 14:41 ` [PATCH RFC 0/3] arm64: disable/enable d-cache support for Pratyush Anand
2015-05-06 17:05 ` Geoff Levand
2015-05-06 17:37 ` Pratyush Anand
2015-05-07 4:25 ` AKASHI Takahiro
2015-05-07 4:54 ` Pratyush Anand [this message]
2015-05-07 5:08 ` AKASHI Takahiro
2015-05-07 15:32 ` 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=554AEFF7.5070300@redhat.com \
--to=panand@redhat.com \
--cc=geoff@infradead.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