From: Matt Spinler <mspinler@linux.ibm.com>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Vijay Khemka <vijaykhemkalinux@gmail.com>
Subject: Re: hardcoded median function in phosphor-virtual-sensor
Date: Tue, 5 Jan 2021 08:18:47 -0600 [thread overview]
Message-ID: <0098a230-acaf-173d-3e12-ede57cfcc563@linux.ibm.com> (raw)
In-Reply-To: <CAGm54UFFJ5Rd=4v9X3LBP_Mp5LbkQrBFtT0-PeMGumzF8kdN0A@mail.gmail.com>
On 1/4/2021 8:34 PM, Lei Yu wrote:
> On Tue, Jan 5, 2021 at 6:58 AM Matt Spinler <mspinler@linux.ibm.com> wrote:
>>> whose values must be defined in entity-manager. Since exprtk
>>> expressions are not allowed in
>>> entity-manager, I cannot just port the PVS's JSON config into an
>>> entity-manager config.
>>>
>>> I missed this discussion but why can't we simply use virtual sensor as
>>> expertk provides median function and we have threshold support for
>>> each virtual sensor. Please help, if I am missing anything.
> I did not notice the discussion as well.
> From my understanding, the exprtk is defined in the json config
> (/usr/share/phosphor-virtual-sensor/virtual_sensor_config.json), and
> technically we could use any expression that exprtk supports.
> e.g. we use max() in our system (see below example), which is not
> upstreamed yet but it works well.
> "Expression": "max(T0, T1, T2)"
Yea, I agree, what you have here is exactly how PVS was designed to be used.
My goal was to add support to have its config be able to be defined in
the entity manager JSON instead, which is what is driving the work of
needing
selectable expressions based on the name.
next prev parent reply other threads:[~2021-01-05 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 17:48 hardcoded median function in phosphor-virtual-sensor Matt Spinler
2021-01-04 20:54 ` Vijay Khemka
2021-01-04 22:57 ` Matt Spinler
2021-01-05 2:34 ` Lei Yu
2021-01-05 14:18 ` Matt Spinler [this message]
2021-01-05 14:27 ` Patrick Williams
2021-01-05 15:56 ` Matt Spinler
2021-01-05 17:18 ` Vijay Khemka
2021-01-05 17:28 ` Matt Spinler
2021-01-05 17:38 ` Ed Tanous
2021-01-05 20:23 ` Patrick Williams
2021-01-05 20:20 ` Patrick Williams
2021-01-05 17:31 ` Ed Tanous
2021-01-05 17:30 ` 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=0098a230-acaf-173d-3e12-ede57cfcc563@linux.ibm.com \
--to=mspinler@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vijaykhemkalinux@gmail.com \
--cc=yulei.sh@bytedance.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 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.