From: Sodagudi Prasad <psodagud@codeaurora.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
julien.thierry@arm.com, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
sudeep.holla@arm.com, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kernel/panic: Use SYSTEM_RESET2 command for warm reset
Date: Fri, 17 May 2019 11:03:25 -0700 [thread overview]
Message-ID: <caa4ee48af33b320d8a1bcdbb974ada8@codeaurora.org> (raw)
In-Reply-To: <20190516182949.GD10985@darkstar.musicnaut.iki.fi>
On 2019-05-16 11:29, Aaro Koskinen wrote:
> Hi,
>
> On Wed, May 08, 2019 at 06:47:12PM -0700, Prasad Sodagudi wrote:
>> Some platforms may need warm reboot support when kernel crashed
>> for post mortem analysis instead of cold reboot. So use config
>> CONFIG_WARM_REBOOT_ON_PANIC and SYSTEM_RESET2 psci command
>> support for warm reset.
>
> Please see commit b287a25a7148 - you can now use kernel command
> line option reboot=panic_warm to get this.
Thanks Aaro. Yes. I can use this option. Thanks Sudeep and all for
discussing.
>
> A.
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
Linux Foundation Collaborative Project
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-17 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 21:44 PSCI version 1.1 and SYSTEM_RESET2 Sodagudi Prasad
2019-05-01 0:07 ` Sodagudi Prasad
2019-05-01 9:49 ` Sudeep Holla
2019-05-01 18:43 ` Sodagudi Prasad
2019-05-02 9:05 ` Sudeep Holla
2019-05-09 1:38 ` Sodagudi Prasad
2019-05-09 1:47 ` [PATCH] kernel/panic: Use SYSTEM_RESET2 command for warm reset Prasad Sodagudi
2019-05-09 9:40 ` Sudeep Holla
2019-05-16 18:29 ` Aaro Koskinen
2019-05-17 18:03 ` Sodagudi Prasad [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=caa4ee48af33b320d8a1bcdbb974ada8@codeaurora.org \
--to=psodagud@codeaurora.org \
--cc=aaro.koskinen@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=julien.thierry@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@arm.com \
--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 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).