From: Geoff Levand <geoff@infradead.org>
To: Pratyush Anand <panand@redhat.com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>, kexec@lists.infradead.org
Subject: Re: [PATCH RFC 0/3] arm64: disable/enable d-cache support for
Date: Thu, 07 May 2015 08:32:06 -0700 [thread overview]
Message-ID: <1431012726.12082.28.camel@infradead.org> (raw)
In-Reply-To: <554AEFF7.5070300@redhat.com>
On Thu, 2015-05-07 at 10:24 +0530, Pratyush Anand wrote:
> @Geoff: Do you see any specific side effect for enabling D-cache in
> purgatory, other than the fact that it increases size of purgatory? May
> be we can keep an user option to select/not select d-cache enabling.
The checks in purgatory are for kdump, which won't be a regularly used
feature. I don't want to add the complexity to save one minute for
someone who will likely spend several hours working on a problem that
triggered a kdump.
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2015-05-07 15:32 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
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 [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=1431012726.12082.28.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