linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stewart@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
	joel@jms.id.au
Subject: Re: [PATCH v2 1/2] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform
Date: Thu, 14 May 2015 01:47:04 +0530	[thread overview]
Message-ID: <5553B140.4090401@linux.vnet.ibm.com> (raw)
In-Reply-To: <1431326992.31935.1.camel@ellerman.id.au>


On 05/11/2015 12:19 PM, Michael Ellerman wrote:
> On Thu, 2015-05-07 at 15:00 +0530, Vipin K Parashar wrote:
>> This patch adds support for FSP EPOW (Early Power Off Warning) and
>> DPO (Delayed Power Off) events support 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 shutdown request.
>> 	This patch enables host kernel on PowerNV platform to handle OPAL
>> notifications for these events and initiate system poweroff. Since EPOW
>> notifications are sent in advance of impending shutdown event and thus
>> this patch also adds functionality to wait for EPOW condition to return to
>> normal. Host allows MAX_POWEROFF_SYS_TIME (600 seconds) as system
>> poweroff time (time for host + guests shutdown) and waits for remaining
>> time for EPOW condition to return to normal. If EPOW condition doesn't
>> return to normal in calculated time it proceeds with graceful system
>> shutdown. For EPOW events with smaller timeouts values than
>> MAX_POWEROFF_SYS_TIME it proceeds with system shutdown without any wait
>> for EPOW condition to return to normal.
>
> Can I suggest an alternative design:
>   - when we recieve a DPO event call orderly_poweroff()
>   - when we recieve an EPOW event call orderly_poweroff()
>
> Thoughts?

Will make changes as per suggested design above and sent out patch.

>
> cheers
>
>

  parent reply	other threads:[~2015-05-13 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  9:30 [PATCH v2 0/2] Poweroff (EPOW, DPO) events support for PowerNV platform Vipin K Parashar
2015-05-07  9:30 ` [PATCH v2 1/2] powerpc/powernv: Add poweroff " Vipin K Parashar
2015-05-08  1:26   ` Joel Stanley
2015-05-11  7:01     ` Vipin K Parashar
2015-05-08  7:37   ` trigg
2015-05-11 22:31     ` Stewart Smith
     [not found]       ` <CAPfuKjKtSHB3Q03vGD9XDnk2yFV31mC8wdJGr3q8XYZfvSx3LA@mail.gmail.com>
2015-05-12 17:09         ` Triggering
2015-05-11  6:49   ` Michael Ellerman
2015-05-11  9:01     ` Vipin K Parashar
2015-05-11 10:47       ` Vipin K Parashar
2015-05-13 20:17     ` Vipin K Parashar [this message]
2015-05-07  9:30 ` [PATCH v2 2/2] powerpc/powernv: Extract EPOW events timeout values from OPAL device tree 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=5553B140.4090401@linux.vnet.ibm.com \
    --to=vipin@linux.vnet.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=stewart@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).