From: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org, bradleyb@fuzziesquirrel.com
Subject: Implement IPMI POH functionality
Date: Mon, 26 Mar 2018 17:29:25 +0530 [thread overview]
Message-ID: <24f546e1-4766-e6f0-df54-eaa399ae7189@linux.vnet.ibm.com> (raw)
Hi,
I would be explaining a rough idea of how we plan to go about,
This is related to https://github.com/openbmc/openbmc/issues/2979
Please share your thoughts and feedback on this proposal.
=>we were planning to add the property in the chassis interface
which tells that since how many hours chassis was powered on.
=>This property gets updated by internal timer which wakes up after
an hour and updates this property if chassis is powered on.
1) Should we set the uptime to 0 if chassis state has been
transitioned from
PowerOn-->PowerOff
or
2) Don't update this property for the chassis power off duration and
update
this property when the chassis state changes to PowerOn.
What is community view on this?
Our opinion is that we should go with option 2 as other
implementation(AMI)
does the same.
=> In factory reset case this property will reset to 0.
=>If BMC has been rebooted due to any reason,This property will not
get updated for that duration and when BMC comes back,This timer
kicks off and updates this property and it would be cumulative
on what was the earlier value before BMC reboot.
=> Chassis object would be saved in nonvolatile storage to keep the last
POH counter value.
=> Get functionality would be allowed,set would not be allowed from IPMI
interface.
Regards
Ratan Gupta
next reply other threads:[~2018-03-26 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 11:59 Ratan Gupta [this message]
2018-03-27 1:41 ` Implement IPMI POH functionality Emily Shaffer
2018-03-28 12:56 ` Alexander Amelkin
2018-03-28 13:38 ` Brad Bishop
2018-03-28 14:01 ` Alexander Amelkin
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=24f546e1-4766-e6f0-df54-eaa399ae7189@linux.vnet.ibm.com \
--to=ratagupt@linux.vnet.ibm.com \
--cc=bradleyb@fuzziesquirrel.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.