From: Pratyush Anand <panand@redhat.com>
To: Geoff Levand <geoff@infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
james.morse@arm.com, Ruslan Bilovol <ruslan.bilovol@gmail.com>,
bauerman@linux.vnet.ibm.com, dyoung@redhat.com,
kexec@lists.infradead.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v23 0/9] arm64: add kdump support
Date: Fri, 29 Jul 2016 22:47:35 +0530 [thread overview]
Message-ID: <20160729171735.GC478@localhost.localdomain> (raw)
In-Reply-To: <1469812107.16559.37.camel@infradead.org>
On 29/07/2016:10:08:27 AM, Geoff Levand wrote:
> Hi,
>
> On Fri, 2016-07-29 at 19:26 +0300, Ruslan Bilovol wrote:
>
> > Also for some reason in case of 'load and kexec the kernel' it
> > takes 1-2 minutes to start booting after I do kexec -e, need to
> > investigate it further.
>
> You could try my patch ("purgatory: Change default sha256
> optimization to -O2") in my master branch:
Yep, that did bring my 2 Min 30 sec to almost 20 sec, and then it came down to
fraction of second after D-cache enabling.
~Pratyush
>
> https://git.kernel.org/cgit/linux/kernel/git/geoff/kexec-tools.git/log/
>
> Other have said it helped.
>
> -Geoff
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v23 0/9] arm64: add kdump support
Date: Fri, 29 Jul 2016 22:47:35 +0530 [thread overview]
Message-ID: <20160729171735.GC478@localhost.localdomain> (raw)
In-Reply-To: <1469812107.16559.37.camel@infradead.org>
On 29/07/2016:10:08:27 AM, Geoff Levand wrote:
> Hi,
>
> On Fri, 2016-07-29 at 19:26 +0300, Ruslan Bilovol wrote:
>
> > Also for some reason in case of 'load and kexec the kernel' it
> > takes 1-2 minutes to start booting after I do kexec -e, need to
> > investigate it further.
>
> You could try my patch ("purgatory: Change default sha256
> optimization to -O2") in my master branch:
Yep, that did bring my 2 Min 30 sec to almost 20 sec, and then it came down to
fraction of second after D-cache enabling.
~Pratyush
>
> https://git.kernel.org/cgit/linux/kernel/git/geoff/kexec-tools.git/log/
>
> Other have said it helped.
>
> -Geoff
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-07-29 17:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 7:56 [PATCH v23 0/9] arm64: add kdump support AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 1/9] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 2/9] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 3/9] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 4/9] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 5/9] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 6/9] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 7/9] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 7:56 ` [PATCH v23 8/9] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-26 7:56 ` AKASHI Takahiro
2016-07-26 8:02 ` [PATCH v23 9/9] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2016-07-26 8:02 ` AKASHI Takahiro
2016-07-26 8:02 ` AKASHI Takahiro
2016-07-27 15:09 ` Rob Herring
2016-07-27 15:09 ` Rob Herring
2016-07-27 15:09 ` Rob Herring
[not found] ` <20160728075511.GA7995@linaro.org>
2016-08-04 5:10 ` AKASHI Takahiro
2016-08-04 5:10 ` AKASHI Takahiro
2016-08-04 5:10 ` AKASHI Takahiro
2016-07-26 8:09 ` [PATCH v23 0/9] arm64: add kdump support AKASHI Takahiro
2016-07-26 8:09 ` AKASHI Takahiro
2016-07-29 16:26 ` Ruslan Bilovol
2016-07-29 16:26 ` Ruslan Bilovol
2016-07-29 17:08 ` Geoff Levand
2016-07-29 17:08 ` Geoff Levand
2016-07-29 17:17 ` Pratyush Anand [this message]
2016-07-29 17:17 ` Pratyush Anand
2016-07-29 17:13 ` Pratyush Anand
2016-07-29 17:13 ` Pratyush Anand
2016-08-01 4:37 ` AKASHI Takahiro
2016-08-01 4:37 ` AKASHI Takahiro
2016-08-01 6:21 ` Pratyush Anand
2016-08-01 6:21 ` Pratyush Anand
2016-08-01 6:46 ` AKASHI Takahiro
2016-08-01 6:46 ` AKASHI Takahiro
2016-08-04 5:20 ` AKASHI Takahiro
2016-08-04 5:20 ` AKASHI Takahiro
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=20160729171735.GC478@localhost.localdomain \
--to=panand@redhat.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=ruslan.bilovol@gmail.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.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.