All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: kunyi731@gmail.com, anoo@us.ibm.com, benjaminfair@google.com,
	openbmc@lists.ozlabs.org, ed@tanous.net, gmills@linux.ibm.com,
	vishwa@linux.ibm.com,
	Supreeth Venkatesh <supreeth.venkatesh@amd.com>,
	jason.m.bills@linux.intel.com, vijaykhemka@fb.com,
	wak@google.com
Subject: Re: Progress Codes in BMC
Date: Mon, 1 Feb 2021 20:45:50 -0600	[thread overview]
Message-ID: <YBi83kwe6SZqkcq0@heinlein> (raw)
In-Reply-To: <20210202002139.jsjkl4icge5bf5cb@thinkpad.fuzziesquirrel.com>

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

On Mon, Feb 01, 2021 at 07:21:39PM -0500, Brad Bishop wrote:
> On Sat, Jan 30, 2021 at 08:31:26AM -0600, Patrick Williams wrote:
> >On Wed, Jan 27, 2021 at 08:05:26PM -0500, Brad Bishop wrote:
> >>
> >> There are multiple sources of the codes - on Power the power sequencing
> >> is done on the BMC and that is considered part of the server boot so we
> >> have both those applications indicating their progress along with the
> >> more traditional progress flowing down from system firmware.
> >
> >The `xyz.openbmc_project.State.Boot.Raw` is the interface to use here.
> >You just write the `Value` property.  
> 
> Ok.  Do I have it right - on any application that wants to post a 
> "progress code" you would just implement this interface on a single 
> (arbitrary?) path and continually write to the Value property?

I think it is even simpler than that.  You just need to make a dbus
client call to write to the Boot.Raw value.  This might happen from your
boot sequence on the BMC-side or from PLDM for the Host-side.

You will want the phosphor-post-code-manager application running, which will
listen to the PropertyChanged signals from Boot.Raw and keep the running
history for you.

There is also phosphor-host-postd.  Currently it has an implementation
that looks at LPC to get the post codes.  There was a proposed
implementation [1] that added multi-host support and I think support to
get the value directly from dbus client writes to Boot.Raw instead of
the lpc-snoop method.  Then there is code in fb-ipmi-oem that writes the
results of some IPMB messages into the Boot.Raw value[2].  Looking at
this I'm not positive that all the pieces are all there, but I think it
is mostly there.  Maybe check with the author on 1 to see where it is
at.

This design doc might be useful too [3].

1. https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-postd/+/36509
2. https://github.com/openbmc/fb-ipmi-oem/blob/master/src/biccommands.cpp#L76
3. https://github.com/openbmc/docs/blob/master/designs/multi-host-postcode.md

-- 
Patrick Williams

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

  parent reply	other threads:[~2021-02-02  2:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 11:53 Progress Codes in BMC manoj kiran
2021-01-22 12:32 ` Deepak Kodihalli
2021-01-22 14:18   ` Supreeth Venkatesh
2021-01-22 14:52     ` Patrick Williams
2021-01-25  2:24       ` chunhui.jia
2021-01-25  5:29         ` Venkatesh, Supreeth
2021-01-26  4:05           ` chunhui.jia
2021-01-28  1:05       ` Brad Bishop
2021-01-30 14:31         ` Patrick Williams
2021-02-02  0:21           ` Brad Bishop
2021-02-02  0:49             ` Ed Tanous
2021-02-02  1:08               ` Brad Bishop
2021-02-02  1:44                 ` Ed Tanous
2021-02-02  2:45             ` Patrick Williams [this message]
2021-02-04  8:47               ` manoj kiran
2021-02-04  9:34                 ` Deepak Kodihalli
2021-02-04 10:22                   ` manoj kiran
2021-02-04 12:17                     ` Deepak Kodihalli
2021-01-28 18:03     ` Benjamin Fair
2021-01-28 18:17       ` Supreeth Venkatesh

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=YBi83kwe6SZqkcq0@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=anoo@us.ibm.com \
    --cc=benjaminfair@google.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=ed@tanous.net \
    --cc=gmills@linux.ibm.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=kunyi731@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=supreeth.venkatesh@amd.com \
    --cc=vijaykhemka@fb.com \
    --cc=vishwa@linux.ibm.com \
    --cc=wak@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.