All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Will Liang (梁永鉉)" <Will.Liang@quantatw.com>
To: Andrew Jeffery <andrew@aj.id.au>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Stefan M Schaeckeler <sschaeck@cisco.com>,
	"dkodihal@in.ibm.com" <dkodihal@in.ibm.com>
Subject: RE: ECC memory of BMC
Date: Fri, 22 Feb 2019 02:00:01 +0000	[thread overview]
Message-ID: <8f0d3dec56434a0484f6d5172c036ed4@quantatw.com> (raw)
In-Reply-To: <8b3b8d3a-9cf5-4f7d-9993-e71fd3cd6e07@www.fastmail.com>

> 
> On Thu, 21 Feb 2019, at 17:57, Will Liang (梁永鉉) wrote:
> >
> > Hi Andrew,
> >
> > Thanks for your response.
> >
> > We have also found EDAC driver.
> >
> > What we want to do is to record the ECC events to SEL.
> >
> > we are considering to create new dbus and a service.
> 
> Right; I think you need to create a new service that polls the sysfs interface for
> the EDAC device, and then use phosphor-logging to create error logs. 


We consider creating the following objects for D-Bus:
-bus name : /xyz/openbmc_project/ECC
-object path : /xyz/openbmc_project/ECC/status
-interface : xyz.openbmc_project.Memory.MemoryECC

and error types for xyz::openbmc_project::Memory::Ecc::Error::ceCount and "ueCount"
and "isLoggingLimitReached" for phosphor-logging error message.

 I'm not
> much of a userspace guy, so I've Cc'ed Deepak who might be able to help on
> that  front.
>

> Andrew

  reply	other threads:[~2019-02-22  2:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21  6:25 ECC memory of BMC Will Liang (梁永鉉)
2019-02-21  7:10 ` Andrew Jeffery
2019-02-21  7:27   ` Will Liang (梁永鉉)
2019-02-21 16:56     ` Stefan Schaeckeler (sschaeck)
2019-02-22  5:52       ` Stefan Schaeckeler (sschaeck)
2019-02-22  7:48         ` Will Liang (梁永鉉)
2019-02-22  0:28     ` Andrew Jeffery
2019-02-22  2:00       ` Will Liang (梁永鉉) [this message]
2019-02-22  5:52         ` Stefan Schaeckeler (sschaeck)
2019-02-22  5:55           ` Andrew Jeffery
2019-02-22  6:37             ` Will Liang (梁永鉉)

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=8f0d3dec56434a0484f6d5172c036ed4@quantatw.com \
    --to=will.liang@quantatw.com \
    --cc=andrew@aj.id.au \
    --cc=dkodihal@in.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sschaeck@cisco.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.