From: Geoff Levand <geoff@infradead.org>
To: Pratyush Anand <panand@redhat.com>, kexec@lists.infradead.org
Cc: james.morse@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility
Date: Tue, 22 Nov 2016 10:56:59 -0800 [thread overview]
Message-ID: <8415f028-f42e-2980-9b60-e85aae046d02@infradead.org> (raw)
In-Reply-To: <cover.1479788404.git.panand@redhat.com>
Hi Pratyush,
On 11/21/2016 08:32 PM, Pratyush Anand wrote:
> It takes more that 2 minutes to verify SHA in purgatory when vmlinuz image
> is around 13MB and initramfs is around 30MB. It takes more than 20 second
> even when we have -O2 optimization enabled. However, if dcache is enabled
> during purgatory execution then, it takes just a second in SHA verification.
As I had mentioned in another thread, I think -O2 optimization is
sufficient considering the complexity of the code needed to enable
the dcache. Integrity checking is only needed for crash dump
support. If the crash reboot takes an extra 20 seconds does it
matter?
For the re-boot of a stable system where the new kernel is loaded
then immediately kexec'ed into integrity checking is not needed.
For that arm64 support needs to be added to kexec-lite.
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-11-22 18:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 4:32 [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Pratyush Anand
2016-11-22 4:32 ` [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2016-11-25 18:30 ` James Morse
2016-12-14 9:38 ` Pratyush Anand
2016-12-14 10:12 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:37 ` Mark Rutland
2016-12-14 12:11 ` James Morse
2016-12-14 12:21 ` Pratyush Anand
2016-12-14 13:44 ` Mark Rutland
2016-12-14 14:13 ` Pratyush Anand
2016-12-14 12:13 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:28 ` Mark Rutland
2016-11-22 4:32 ` [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Pratyush Anand
2016-11-22 18:57 ` Geoff Levand
2016-11-23 1:46 ` Pratyush Anand
2016-11-23 2:03 ` Dave Young
2016-11-23 2:11 ` Pratyush Anand
2016-11-23 8:08 ` Simon Horman
2016-11-23 8:17 ` Pratyush Anand
2016-11-22 18:56 ` Geoff Levand [this message]
2016-11-23 1:39 ` [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Pratyush Anand
2016-11-25 18:30 ` James Morse
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=8415f028-f42e-2980-9b60-e85aae046d02@infradead.org \
--to=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=panand@redhat.com \
/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