From: Geoff Levand <geoff@infradead.org>
To: Pratyush Anand <panand@redhat.com>
Cc: takahiro.akashi@linaro.org, kexec@lists.infradead.org
Subject: Re: [PATCH RFC 0/3] arm64: disable/enable d-cache support for
Date: Wed, 06 May 2015 10:05:59 -0700 [thread overview]
Message-ID: <1430931959.12082.12.camel@infradead.org> (raw)
In-Reply-To: <cover.1430742915.git.panand@redhat.com>
Hi,
I don't really like the idea of doing cache operations in purgatory.
For fast reboot we have the --lite option to kexec, which will skip the
digest calculations.
Your 2 minutes seems like a long time. Is this seen on other platforms?
-Geoff
On Mon, 2015-05-04 at 18:32 +0530, Pratyush Anand wrote:
> These patches add support for enable/disable d cache support. It reduces
> time for sha verification from more than 2 min to 3-4 sec on my
> platform.
> There are some of the observation which I am unable to explain.
> * It takes around 18 sec when I boot a kexec kernel and around 3-4 sec
> * when I boot a crash kernel. In case of kexec kernel start of 1st
> * segment is at 0000004000280000 and, end of last segment is at
> * 00000040029c0000. In case of crash kernel start of 1st segment is at
> * 00000041b9080000 and, end of last segment is at 00000041f9000000.
>
> Pratyush Anand (3):
> arm64: Add enable/disable d-cache support for purgatory
> arm64: Pass RAM boundary to purgatory
> arm64: Enable/disable D-cache before/after sha verification
>
> kexec/arch/arm64/include/types.h | 16 +++
> kexec/arch/arm64/kexec-arm64.c | 16 ++-
> purgatory/arch/arm64/Makefile | 1 +
> purgatory/arch/arm64/cache.S | 222 +++++++++++++++++++++++++++++++++
> purgatory/arch/arm64/cache.h | 42 +++++++
> purgatory/arch/arm64/entry.S | 10 ++
> purgatory/arch/arm64/purgatory-arm64.c | 12 ++
> 7 files changed, 318 insertions(+), 1 deletion(-)
> create mode 100644 kexec/arch/arm64/include/types.h
> create mode 100644 purgatory/arch/arm64/cache.S
> create mode 100644 purgatory/arch/arm64/cache.h
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-05-06 17:05 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 [this message]
2015-05-06 17:37 ` Pratyush Anand
2015-05-07 4:25 ` AKASHI Takahiro
2015-05-07 4:54 ` Pratyush Anand
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=1430931959.12082.12.camel@infradead.org \
--to=geoff@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=panand@redhat.com \
--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