All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Patrick Venture <venture@google.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: thermald for OpenBMC
Date: Mon, 17 Apr 2017 21:31:59 -0500	[thread overview]
Message-ID: <20170418023159.GA25774@heinlein.lan> (raw)
In-Reply-To: <CAO=notwmuHO91eentG60W012rnQXtAybuTPqo+_EbY426eOwSA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

Patrick,

On Mon, Apr 17, 2017 at 01:21:29PM -0700, Patrick Venture wrote:
> I'm working on a thermal control loop that'll operate within the openbmc
> framework(s) and wanted to provide a somewhat high level overview for
> thoughts.

We should connect you with Matt Spinler (mspinler) and Matt Barth
(msbarth) on IRC.  They have been working on implementing the "IBM fan
control algorithm" but I suspect there is a significant amount of
overlap.  Our intention was that you'd be able to reuse our
implementation and insert a different (low-level detailed) algorithm.

> The general design is to have a daemon that reads fans and temperatures
> from dbus (reaching out to phosphor-hwmon) as well as being able to receive
> temperatures and other sensor information over an OEM IPMI command.

Sounds good.  This is how it is suppose to work.

For the IPMI commands, the expectation would be that either the IPMI
provider or an application fed by the IPMI provider for these OEM
commands would implement the same xyz.openbmc_project.Sensor.Value
interface as the phosphor-hwmon.  This way the thermal algorithm really
doesn't need to know where the data comes from.

> The system will support zones defined (yes, probably in YAML).  A zone will
> have at least one exclusion fan, and at least one thermal sensor.  The
> thermal sensor can be shared.  There will be defaults provided in this
> configuration to act as fallbacks.

There is some code available to define zones via YAML.  Matt Spinler can
point you at these.

> The thermal loop will be margin based and attempt to drive the fans to
> maintain the temperature within operating temperature of the zones.  Each
> zone will be independently managed.

These sounds very similar to what their intended design is as well.  For
a zone there is a lower-threshold and an upper-threshold.  When the
temperature is above the upper-threshold, the fan speed is increased and
the fans are decreased when the temperature is below the
lower-threshold.  Again, the Matts can give you details on what the "IBM
fan control algorithm" design is.

> Because not all thermal sensors can necessarily be ready by the BMC, we
> need a method of getting that information from the host.  From a previous
> project, we have the notion of sending thermal margins for slow and quick
> (heat change) devices to a controller.

Is this the Host->BMC via IPMI you mentioned earlier or does the BMC
need to actively query the host in some cases?  Hopefully it is always
one direction.

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-04-18  2:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 20:21 thermald for OpenBMC Patrick Venture
2017-04-18  2:31 ` Patrick Williams [this message]
2017-04-18  3:20   ` Patrick Venture
2017-05-02 18:07     ` OpenBMC Thermal Design Matthew Barth
2017-05-02 19:33       ` Patrick Venture
2017-05-02 20:46         ` Patrick Venture
2017-05-02 21:21         ` Matthew Barth
2017-05-02 21:33           ` Patrick Venture
2017-05-03 14:05             ` Matthew Barth

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=20170418023159.GA25774@heinlein.lan \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.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.