All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Andrew Geissler <geissonator@gmail.com>,
	Andrew Jeffery <andrew@aj.id.au>
Cc: jdking@us.ibm.com, OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: BMC and Host State Management Refactor
Date: Wed, 04 Jan 2017 11:07:55 +1100	[thread overview]
Message-ID: <87zij7r8kk.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CALLMt=o6td6kAprcHxTyq628mrDk-aAXaK-D_0A9kA+iwVUbUA@mail.gmail.com>

Andrew Geissler <geissonator@gmail.com> writes:
> 4. Provide a softReboot and hardReboot option in the host state code.
> The hardReboot would do the chassis power off (hard power off) and
> then power on.  The softReboot will work as expected and issue the
> soft power down command to the host.
> - Seems like a happy compromise in where the logic goes.  Checkstop is
> smart enough to know it needs a hardReboot and host state code knows
> how to do it.

So, we also have fast reset, which is different again, mostly in that it
has slightly different security implications.

So, we have power (off|cycle) with hard/soft shutdown and we have reboot with
hard/soft shutdown.

At least on other platforms, I think there's a similar concept, as I've
noticed that on many x86 systems if you don't cut the power on reboot,
you skip some of the POST....

thougths?

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2017-01-04  0:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 20:31 BMC and Host State Management Refactor Andrew Geissler
2016-11-21  5:55 ` Joel Stanley
2016-11-22  2:28   ` Andrew Geissler
2016-11-22  3:40     ` Andrew Jeffery
2016-11-22 17:23       ` Andrew Geissler
2016-11-23  1:07         ` Andrew Jeffery
2016-11-28  2:30           ` Andrew Geissler
2017-01-03 22:24             ` Andrew Geissler
2017-01-04  0:07               ` Stewart Smith [this message]
2017-01-04 16:28               ` Patrick Williams
2017-01-04 22:44                 ` Andrew Geissler

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=87zij7r8kk.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=geissonator@gmail.com \
    --cc=jdking@us.ibm.com \
    --cc=openbmc@lists.ozlabs.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 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.