From: trigg <mr.triggtrigg@gmail.com>
To: Vipin K Parashar <vipin@linux.vnet.ibm.com>
Cc: "stewart@linux.vnet.ibm.com" <stewart@linux.vnet.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"joel@jms.id.au" <joel@jms.id.au>
Subject: Re: [PATCH v5] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform
Date: Tue, 19 May 2015 18:45:55 +0530 [thread overview]
Message-ID: <9489704C-D4EE-481D-A191-AEAEC10A1ED9@gmail.com> (raw)
In-Reply-To: <1431962284-12260-2-git-send-email-vipin@linux.vnet.ibm.com>
> On 18-May-2015, at 20:48, Vipin K Parashar <vipin@linux.vnet.ibm.com> wrot=
e:
>=20
> This patch adds support for FSP EPOW (Early Power Off Warning) and
> DPO (Delayed Power Off) events for PowerNV platform. EPOW events are
> generated by SPCN/FSP due to various critical system conditions that
> need system shutdown. Few examples of these conditions are high
> ambient temperature or system running on UPS power with low UPS battery.
> DPO event is generated in response to admin initiated system request.
> Upon receipt of EPOW and DPO events host kernel invokes
> orderly_poweroff for performing graceful system shutdown. System admin
> can also add systemd service shutdown scripts to perform any specific
> actions like graceful guest shutdown upon system poweroff. libvirt-guests
> is systemd service available on recent distros for management of guests
> at system start/shutdown time.
>=20
> Signed-off-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>
Acked-by: trigg <mr.triggtrigg@gmail.com>=
next prev parent reply other threads:[~2015-05-19 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 15:18 [PATCH v5] powerpc/powernv: Poweroff (EPOW, DPO) events support for PowerNV platform Vipin K Parashar
2015-05-18 15:18 ` [PATCH v5] powerpc/powernv: Add poweroff " Vipin K Parashar
2015-05-19 13:15 ` trigg [this message]
2015-06-02 9:16 ` Michael Ellerman
2015-06-02 5:20 ` Vipin K Parashar
2015-06-03 3:41 ` Vaibhav Jain
2015-06-03 5:13 ` [v5] " Michael Ellerman
2015-06-03 19:12 ` Vipin K Parashar
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=9489704C-D4EE-481D-A191-AEAEC10A1ED9@gmail.com \
--to=mr.triggtrigg@gmail.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.com \
--cc=vipin@linux.vnet.ibm.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).