From: Simon Horman <horms@verge.net.au>
To: Geoff Levand <geoff@infradead.org>
Cc: Pratyush Anand <panand@redhat.com>, kexec@lists.infradead.org
Subject: Re: [PATCH V2] purgatory: Change default sha256 optimization to -O2
Date: Fri, 2 Dec 2016 09:21:58 +0100 [thread overview]
Message-ID: <20161202082158.GC32351@verge.net.au> (raw)
In-Reply-To: <e64cbdf7-36f9-c97e-a243-e66350b55661@infradead.org>
On Thu, Dec 01, 2016 at 11:09:37AM -0800, Geoff Levand wrote:
> Change the default purgatory sha256 code optimization from -O0 to -O2, and add a
> new arch specific makefile variable $(ARCH)_PURGATORY_SHA256_CFLAGS which can
> over ride this default. Set ia64_PURGATORY_SHA256_CFLAGS to -O0 to retain the
> previous optimization level for ia64.
>
> The purgatory sha256 code needs the be built with -O0 for the ia64
> architecture. Currently this code is built with -O0 for all architectures,
> which slows down the calculations for architectures which could otherwise
> use -O2.
>
> On arm64, it takes around 20 second to verify SHA in purgatory when
> vmlinuz image is around 13MB and initramfs is around 30M with -O2
> enabled. Otherwise, it takes more than 2 minutes.
>
> Cc: Pratyush Anand <panand@redhat.com>
> Signed-off-by: Geoff Levand <geoff@infradead.org>
Thanks, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-12-02 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:57 [PATCH] purgatory: Change default sha256 optimization to -O2 Geoff Levand
2016-11-24 7:53 ` Simon Horman
2016-11-28 5:44 ` Pratyush Anand
2016-11-30 11:02 ` Simon Horman
2016-12-01 19:09 ` Geoff Levand
2016-12-01 19:09 ` [PATCH V2] " Geoff Levand
2016-12-02 8:21 ` Simon Horman [this message]
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=20161202082158.GC32351@verge.net.au \
--to=horms@verge.net.au \
--cc=geoff@infradead.org \
--cc=kexec@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