From: Pratyush Anand <panand@redhat.com>
To: kexec@lists.infradead.org
Cc: geoff@infradead.org, takahiro.akashi@linaro.org,
horms@verge.net.au, james.morse@arm.com, jk@ozlabs.org,
scottwood@freescale.com, dyoung@redhat.com, vgoyal@redhat.com,
ebiederm@xmission.com
Subject: [PATCH RFC V2 0/2] kexec: arm64: purgatory: cache support
Date: Tue, 12 Jan 2016 10:42:49 +0530 [thread overview]
Message-ID: <cover.1452572612.git.panand@redhat.com> (raw)
This patch series adds support to enable cache during sha-256 verification
in purgatory. Until --enable-dcache is passed to kexec(), these patches
does not affect existing purgatory functionality.
Patches have been tested with Seattle and Mustang for normal kexec and
kdump. It took hardly a second to verify SHA256 when kernel and initramfs
segment sizes were 0x01030000 and 0x01130000 respectively.
Patches are still being sent as RFC, because these are dependent on Geoff's
kexec-tools patches. These patches along with other dependent patches are
also available here:
https://github.com/pratyushanand/kexec-tools.git (HEAD commit 062475cf4f3f)
RFC V1 was here:
http://lists.infradead.org/pipermail/kexec/2015-May/013678.html
Changes since RFC V1:
There had been many changes, I would say rather that code has been
reimplemented. I am listing some of the significant changes here:
-- By default D-cache would be disabled now.
-- Most part of implementation has been moved from asm to c code.
-- Proper synchronization barrier and tlb invalidation
-- Now we can have print during MMU enabled as well, since UART area is
also identity mapped.
-- Supports 64K and 4K page table. If a HW supports 64K then it uses 64K
page implementation, else it checks if 4K is supported and then uses 4K
page table. 16K is not yet supported.
Pratyush Anand (2):
arm64: Add enable/disable d-cache support for purgatory
arm64: Pass RAM boundary and enable-dcache flag to purgatory
kexec/arch/arm64/include/arch/options.h | 6 +-
kexec/arch/arm64/include/types.h | 16 ++
kexec/arch/arm64/kexec-arm64.c | 24 ++-
purgatory/arch/arm64/Makefile | 2 +
purgatory/arch/arm64/cache-asm.S | 228 ++++++++++++++++++++++
purgatory/arch/arm64/cache.c | 333 ++++++++++++++++++++++++++++++++
purgatory/arch/arm64/cache.h | 83 ++++++++
purgatory/arch/arm64/entry.S | 15 ++
purgatory/arch/arm64/purgatory-arm64.c | 10 +-
9 files changed, 714 insertions(+), 3 deletions(-)
create mode 100644 kexec/arch/arm64/include/types.h
create mode 100644 purgatory/arch/arm64/cache-asm.S
create mode 100644 purgatory/arch/arm64/cache.c
create mode 100644 purgatory/arch/arm64/cache.h
--
2.5.0
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2016-01-12 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 5:12 Pratyush Anand [this message]
2016-01-12 5:12 ` [PATCH RFC V2 1/2] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2016-01-12 8:34 ` AKASHI Takahiro
2016-01-12 9:53 ` Pratyush Anand
2016-01-13 4:35 ` AKASHI Takahiro
2016-01-13 5:44 ` Pratyush Anand
2016-01-12 5:12 ` [PATCH RFC V2 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Pratyush Anand
2016-01-12 8:38 ` AKASHI Takahiro
2016-01-12 9:55 ` Pratyush Anand
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=cover.1452572612.git.panand@redhat.com \
--to=panand@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=james.morse@arm.com \
--cc=jk@ozlabs.org \
--cc=kexec@lists.infradead.org \
--cc=scottwood@freescale.com \
--cc=takahiro.akashi@linaro.org \
--cc=vgoyal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.