From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pd0-f182.google.com ([209.85.192.182]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YqE3p-00088R-Az for kexec@lists.infradead.org; Thu, 07 May 2015 05:09:26 +0000 Received: by pdbqa5 with SMTP id qa5so30671231pdb.1 for ; Wed, 06 May 2015 22:09:03 -0700 (PDT) Message-ID: <554AF368.2070104@linaro.org> Date: Thu, 07 May 2015 14:08:56 +0900 From: AKASHI Takahiro MIME-Version: 1.0 Subject: Re: [PATCH RFC 0/3] arm64: disable/enable d-cache support for References: <1430931959.12082.12.camel@infradead.org> <554A5151.7020706@redhat.com> <554AE924.4040208@linaro.org> <554AEFF7.5070300@redhat.com> In-Reply-To: <554AEFF7.5070300@redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Pratyush Anand , Geoff Levand Cc: kexec@lists.infradead.org On 05/07/2015 01:54 PM, Pratyush Anand wrote: > > > On Thursday 07 May 2015 09:55 AM, AKASHI Takahiro wrote: >> Geoff, Pratyush >> >> On 05/07/2015 02:37 AM, Pratyush Anand wrote: >>> Hi Geoff, >>> >>> On Wednesday 06 May 2015 10:35 PM, Geoff Levand wrote: >>>> Your 2 minutes seems like a long time. Is this seen on other platforms? >>> >>> At least it is seen on two different HW platforms I had tested with. I >>> do not know about other. >>> >>> It would be nice if somebody else who is using kexec on HW platform >>> can report their execution time. >> >> On my HW, it took about 42secs before showing extra boot messages after >> "I'm in purgatory." >> > > It would also depend on the size of different segments (mainly kernel and initrd) on which sha256 is calculated. What > are the size of binaries in your case? segment[0].memsz = 0x877000 // kernel segment[1].memsz = 0x4000 // dtb segment[2].memsz = 0x7000 // purgatory no initrd under normal kexec. > In my case: > > segment[0].memsz = 0x10e0000 // kernel > segment[1].memsz = 0x1910000 // initrd > segment[2].memsz = 0x10000 // dtb > segment[3].memsz = 0x40000 // purgatory, not included in sha256 > segment[4].memsz = 0x10000 // elf core hdr Your numbers have extra "0" :) > @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 discussions should be Cc'd to linux-arm-kernel (or at least, arm64 maintainers). -Takahiro AKASHI _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec