From: Kumar Thangavel <kumarthangavel.hcl@gmail.com>
To: openbmc@lists.ozlabs.org
Cc: Zhikui Ren <zhikui.ren@intel.com>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
Andrew Jeffery <andrew@aj.id.au>, Ed Tanous <ed@tanous.net>,
Jayashree D <jayashree-d@hcl.com>,
Amithash Prasad <amithash@fb.com>,
velumanit@hcl.com
Subject: Re: Creating Hard Shutdown interfaces/alarm for NIC Sensor
Date: Mon, 16 Aug 2021 21:27:58 +0530 [thread overview]
Message-ID: <CAA7TbcsaM_nFeA1q=Eq6zsW1gH_73HXSCmtsc=3O0hi2s8QGfA@mail.gmail.com> (raw)
In-Reply-To: <CAA7TbcveKrAFSODfKKJ_q1yaPEZgvn06mBO2tXe7h=Xr6jZHLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Hi All,
Gentle Reminder. Any suggestions/idea on this.
Thanks,
Kumar
On Wed, Aug 11, 2021 at 4:51 PM Kumar Thangavel <
kumarthangavel.hcl@gmail.com> wrote:
> Hi All,
>
>
>
> We have an use case of NIC sensor value goes above 120 (upper non
> recoverable), need to shutdown the slots.
>
>
>
> Critical and Warning interfaces and alarm created based on the
> sensor threshold Severity value. Please refer the below code.
>
>
> https://github.com/openbmc/dbus-sensors/blob/master/src/Thresholds.cpp#L116
>
>
>
> For NIC sensor, planning to create soft and hard shutdown
> interfaces and alarm based on severity value in hwmonTempSensor.
>
>
>
> Already we have Severity 0 for Warning and Severity 1 for
> Critical.
>
> We can have Severity 2 for Softshutdown and Severity 3 for
> Hardshutdown.
>
>
>
> So, Based on the Severity value, the soft and hard shutdown alarm
> will set as true.
>
> Then the sensor-monitor application would take the action based
> on the soft/hard shutdown alarm.
>
>
> Could you please provide your suggestions on this.
>
>
>
> Thanks,
>
> Kumar.
>
[-- Attachment #2: Type: text/html, Size: 3716 bytes --]
next prev parent reply other threads:[~2021-08-16 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 11:21 Creating Hard Shutdown interfaces/alarm for NIC Sensor Kumar Thangavel
2021-08-16 15:57 ` Kumar Thangavel [this message]
2021-08-16 18:54 ` Patrick Williams
2021-08-16 19:32 ` Ed Tanous
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='CAA7TbcsaM_nFeA1q=Eq6zsW1gH_73HXSCmtsc=3O0hi2s8QGfA@mail.gmail.com' \
--to=kumarthangavel.hcl@gmail.com \
--cc=amithash@fb.com \
--cc=andrew@aj.id.au \
--cc=ed@tanous.net \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jayashree-d@hcl.com \
--cc=openbmc@lists.ozlabs.org \
--cc=velumanit@hcl.com \
--cc=zhikui.ren@intel.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).