From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] kexec-tools: arm64: Enable D-cache in purgatory
Date: Fri, 2 Jun 2017 20:02:25 +0530 [thread overview]
Message-ID: <2b80fca3-b462-a1b5-36db-e8b8b8fdc126@redhat.com> (raw)
In-Reply-To: <CAKv+Gu-0p6iWnY9fr67YrYUgiLwArwkNUKio-7XjT0uMafcQ-w@mail.gmail.com>
Hi Ard,
Thanks for all the inputs.
On Friday 02 June 2017 05:14 PM, Ard Biesheuvel wrote:
>> Alternatively, a SHA-256 implementation that uses movz/movk sequences
>> instead of ldr instructions to load the round constants would already
>> be 5x faster, given that we don't need page tables to enable the
>> I-cache.
> Actually, looking at the C code and the objdump of the kernel's
> sha256_generic driver, it is likely that it is already doing this, and
> none of the points I made actually make a lot of sense ...
>
> Pratyush: I assume you are already enabling the I-cache in the purgatory?
It's not enabled yet. But, I had tried first with enabling only I-cache, but
that did not make much difference in execution time.
~Pratyush
next prev parent reply other threads:[~2017-06-02 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 5:02 [PATCH v3 0/2] kexec-tools: arm64: Enable D-cache in purgatory Pratyush Anand
2017-05-23 5:02 ` [PATCH v3 1/2] kexec: arm64: create identity page table to be used " Pratyush Anand
2017-06-02 8:24 ` James Morse
2017-06-02 14:29 ` Pratyush Anand
2017-05-23 5:02 ` [PATCH v3 2/2] arm64: enable d-cache support during purgatory sha verification Pratyush Anand
2017-06-02 8:23 ` [PATCH v3 0/2] kexec-tools: arm64: Enable D-cache in purgatory James Morse
2017-06-02 9:55 ` Ard Biesheuvel
2017-06-02 11:15 ` Bhupesh SHARMA
2017-06-02 11:36 ` Ard Biesheuvel
2017-06-02 11:44 ` Ard Biesheuvel
2017-06-02 14:32 ` Pratyush Anand [this message]
2017-06-02 16:36 ` James Morse
2017-06-02 14:42 ` Pratyush Anand
[not found] ` <CAB=otbT23ySN4VC6G0sBKF5p4SvsnG8PS-C_beBgn8YJUsbw9Q@mail.gmail.com>
2018-04-04 12:45 ` Kostiantyn Iarmak
2018-04-04 13:04 ` Kostiantyn Iarmak
2018-04-04 13:28 ` James Morse
2018-04-04 22:55 ` Ard Biesheuvel
2018-04-05 1:47 ` AKASHI Takahiro
2018-04-06 18:15 ` Kostiantyn Iarmak
2018-04-11 15:59 ` 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=2b80fca3-b462-a1b5-36db-e8b8b8fdc126@redhat.com \
--to=panand@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).