From: Geoff Levand <geoff@infradead.org>
To: Pratyush Anand <panand@redhat.com>, kexec@lists.infradead.org
Cc: james.morse@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory
Date: Tue, 22 Nov 2016 10:57:10 -0800 [thread overview]
Message-ID: <53ee2a62-7822-5457-e59f-e65e64a57019@infradead.org> (raw)
In-Reply-To: <b1b9e70db9d08364040436154cf0cf2f4600da49.1479788404.git.panand@redhat.com>
Hi Pratyush,
On 11/21/2016 08:32 PM, Pratyush Anand wrote:
> When "enable-dcache" is passed to the kexec() command line, kexec-tools
> passes this information to purgatory, which in turn enables cache during
> sha-256 verification.
What's the point of this enable-dcache option? Why not just
always enable the cache if we can?
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-11-22 18:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 4:32 [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Pratyush Anand
2016-11-22 4:32 ` [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2016-11-25 18:30 ` James Morse
2016-12-14 9:38 ` Pratyush Anand
2016-12-14 10:12 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:37 ` Mark Rutland
2016-12-14 12:11 ` James Morse
2016-12-14 12:21 ` Pratyush Anand
2016-12-14 13:44 ` Mark Rutland
2016-12-14 14:13 ` Pratyush Anand
2016-12-14 12:13 ` Pratyush Anand
2016-12-14 11:16 ` James Morse
2016-12-14 11:28 ` Mark Rutland
2016-11-22 4:32 ` [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Pratyush Anand
2016-11-22 18:57 ` Geoff Levand [this message]
2016-11-23 1:46 ` Pratyush Anand
2016-11-23 2:03 ` Dave Young
2016-11-23 2:11 ` Pratyush Anand
2016-11-23 8:08 ` Simon Horman
2016-11-23 8:17 ` Pratyush Anand
2016-11-22 18:56 ` [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Geoff Levand
2016-11-23 1:39 ` Pratyush Anand
2016-11-25 18:30 ` James Morse
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=53ee2a62-7822-5457-e59f-e65e64a57019@infradead.org \
--to=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@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