From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot
Date: Fri, 23 Dec 2016 15:19:04 +1100 [thread overview]
Message-ID: <87pokj2s7b.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <8737iivq6l.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> Andrew Donnellan <andrew.donnellan@au1.ibm.com> writes:
>
>> On 23/11/16 12:37, Andrew Donnellan wrote:
>>>> There's existing logic in kernel/reboot.c to handle a reboot= command
>>>> line parameter, which can set the reboot_mode, so my preference would be
>>>> that we use that.
>>>>
>>>> Currently we completely ignore the reboot_mode, so there's no backward
>>>> compatibility issue.
>>>>
>>>> It looks like the default is REBOOT_COLD, whatever that means. So I
>>>> think we could define that on powernv REBOOT_HARD means "do a full IPL".
>>>
>>> Sounds good.
>>
>> Thinking about this more - you can't change that at runtime. :(
>
> Yeah. Is that a problem? From my POV this is basically a "my firmware is
> broken" workaround, so you're going to want to set it permanently until
> you update your firmware.
The only real world application I can see wanting to do that is perhaps
HTX - where it chooses what kind of bootme run it wants. So, well, for
certain definitions of "real world".
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2016-12-23 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 9:22 [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot Andrew Donnellan
2016-11-22 10:27 ` Michael Ellerman
2016-11-23 1:37 ` Andrew Donnellan
2016-11-23 2:33 ` Andrew Donnellan
2016-11-23 3:19 ` Michael Ellerman
2016-12-23 4:19 ` Stewart Smith [this message]
2016-12-23 4:20 ` Stewart Smith
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=87pokj2s7b.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).