[phosphor-virtual-sensor] Add new feature to get Warning or Critical property
ed at tanous.net
Thu Dec 31 08:03:02 AEDT 2020
On Tue, Dec 29, 2020 at 10:14 PM Harvey Wu (吳崇維) <Harvey.Wu at quantatw.com> wrote:
> Hi Vijay,
> Because I want to calculate the different value between CriticalHigh and current sensor value in CPU sensor, and then there are weighting and some const value to multiply or plus the different value.
> But the CPU sensor critical high threshold temp is set as TjMax, and the TjMax value will be different according the different CPU process type, not a Const. That's why I want to add this feature.
> For example, according the Document below, if the processor is i7-3770K, the TjMax is 105, and if the processor is U7500, the TjMax is 100.
The intent is that these values will be read out of the chip by cpu
sensor, and the cpu sensor critical threshold will be set to 105, and
100 respectively. phosphor-virtual-sensor does not need to be aware
of these thresholds at all, or would only forward on the value closest
to the threshold.
> If the Expression is "(TjMax - currentTemp) * scalar - Const", then it will calculate different results between these two CPU processor.
If we need this, please add this as a feature within CPUSensor. With
that said, I'm still not quite following the use case. Can you
provide more details on what expression you're hoping to write in
phosphor-virtual-sensor, and what the intended behavior is? If your
goal is to implement fan boosting, I believe this is already covered
Could you make more clear what you're trying to accomplish? That will
probably help us give more concrete suggestions.
> Harvey Wu
> From: Vijay Khemka <vijaykhemkalinux at gmail.com>
> Sent: Wednesday, December 30, 2020 1:02 PM
> To: Harvey Wu (吳崇維) <Harvey.Wu at quantatw.com>
> Cc: Lei Yu <yulei.sh at bytedance.com>; openbmc at lists.ozlabs.org
> Subject: Re: [phosphor-virtual-sensor] Add new feature to get Warning or Critical property
> I am not understanding why you want to use threshold values to calculate new sensor values. We can certainly add this feature but it can not be based on name rather we have to think differently to get. It would really help to decide on design once we know it's actual usage. I can't think of any situation here.
> On Tue, Dec 29, 2020 at 6:49 PM Harvey Wu (吳崇維) <mailto:Harvey.Wu at quantatw.com> wrote:
> > On Wed, Dec 30, 2020 at 10:19 AM Harvey Wu (吳崇維)
> > <mailto:Harvey.Wu at quantatw.com> wrote:
> > >
> > > Hi All,
> > >
> > >
> > >
> > > The current phosphor-virtual-sensor DbusParam value is from
> > DBus “Value” property which interface is
> > “xyz.openbmc_project.Sensor.Value”.
> > >
> > > Because I want to get the property “CriticalHigh” value on DBus, could I
> > add a new feature “Interface” property in json file? The property can be
> > “CriticalHigh” , “CriticalLow” , “WarningHigh” or “WarningLow”.
> > According to
> > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
> > com%2Fopenbmc%2Fphosphor-virtual-sensor%2Fblob%2Fmaster%2Fvirtual_
> > sensor_config.json%23L8-L14&data=04%7C01%7CHarvey.Wu%40quantat
> > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw.com%2F&data=04%7C01%7CHarvey.Wu%40quantatw.com%7Cf75707a7431e4dca712e08d8ac80182b%7C179b032707fc4973ac738de7313561b2%7C1%7C0%7C637449013448979318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kxT3i6moVPggqbY1zJiag18Cp9wGmyk1ctqrO8XlTUc%3D&reserved=0%7C1479ebd5aedd4b8a7c3308d8ac6a4393%7C179b032707fc4973ac73
> > 8de7313561b2%7C1%7C0%7C637448919693850853%7CUnknown%7CTWFpb
> > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> > Mn0%3D%7C1000&sdata=0KyrnRkZKr9M59DEg%2BnyUruiege%2B3EDXb
> > mxzR%2B6xeng%3D&reserved=0,
> > the threshold properties are already supported.
> The "Threshold" in json seems only can set the sensor critical or warning value, but I want to use the critical or warning value in "Expression".
> After check the newest commit, this function seems doesn't implement in current source code.
> > --
> > BRs,
> > Lei YU
> Harvey Wu
More information about the openbmc