Hi Geoff,
On Wednesday 23 November 2016 12:26 AM, Geoff Levand wrote:
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?
Even this 20 second for kdump case is also annoying and this could
increase if the size of initramfs increases.
Moreover, by default d-cache is still disabled, so even if it is complex
and you might see some instability, it will not affect the existing
systems. So, IMHO we should have this in the upstream.
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.
I think kexec-lite is a separate project and --lite in kexec-tools was
never acked. So, even for `kexec -l` it will be helpful.
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
