From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Callout definitions in phosphor-logging : RFC
Date: Tue, 31 Jan 2017 10:51:47 +1100 [thread overview]
Message-ID: <87o9youmwc.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <82ebc370-99c2-a44e-bf89-68d90acff3ae@linux.vnet.ibm.com>
Deepak Kodihalli <dkodihal@linux.vnet.ibm.com> writes:
> 4) The error log server, upon identifying a callout, will with the help
> of the callout metadata, the system's MRW and various system policies,
> identify one or more FRUs that need to be called out. It will fetch
> appropriate FRU inventory objects from the phosphor-inventory-manager,
> and create associations between the error object and these inventory
> objects, in order to represent the callouts.
Would this be a hard mapping?
What about calling out a bit of hardware that the BMC does not
necessarily know about? e.g. disks or DIMMS on a PCIe card? Is that
something that should be supported?
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2017-01-30 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:43 Callout definitions in phosphor-logging : RFC Deepak Kodihalli
2017-01-30 23:51 ` Stewart Smith [this message]
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=87o9youmwc.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=dkodihal@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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.