From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: "Will Liang (梁永鉉)" <Will.Liang@quantatw.com>
Cc: "Richard Tung (董彥屏)" <Richard.Tung@quantatw.com>,
"Buddy Huang (黃天鴻)" <Buddy.Huang@quantatw.com>,
"George Hung (洪忠敬)" <George.Hung@quantatw.com>,
"OpenBMC Maillist" <openbmc@lists.ozlabs.org>
Subject: Re: Some questions about "Add option for SEL commands for Journal-based SEL entries"
Date: Fri, 29 Mar 2019 11:14:43 -0700 [thread overview]
Message-ID: <6ba86d1a-ecfa-20a8-9b84-8e855fabf320@linux.intel.com> (raw)
In-Reply-To: <2bcbf6920bc14c0fa1826ac5b0bde62f@quantatw.com>
On 3/29/2019 4:00 AM, Will Liang (梁永鉉) wrote:
> Hi Jason,
>
>
> Sorry to bother you again.
It's not a bother. :)
>
> After solving sensor type and event type problem for discrete
> sensor(memory) , I encountered another issue.
> From the code, it seems only support getting the sensor number of
> threshold-based sensors.
> How do I get the sensor number of discrete sensors?
> Would you have any suggestion or plan to get sensor number of discrete
> sensors?
Unfortunately, you have hit the crux of the issue that is preventing the
journal-based SEL from being fully adopted, which is that we don't have
a flexible, generic way to assign sensor numbers.
If you only need discrete sensors to be assigned numbers dynamically,
you might be able to extend the sensor mapping that is used to get the
number here:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/12951/24/sdrutils.hpp#117.
If you can set a path for your discrete sensors so they are included
in the list, it may solve your issue.
We've discussed some options for a flexible, generic solution that would
work for everyone, but I don't believe any work has been done, yet. You
can view the discussion here:
https://lists.ozlabs.org/pipermail/openbmc/2019-January/014873.html and
in the comments on the review here:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/12951.
Thanks,
-Jason
prev parent reply other threads:[~2019-03-29 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b96ecddbcf4d4b098ca22c3be8c8e819@quantatw.com>
[not found] ` <b4c22fe4-96c6-bf8a-7bf7-184af4122653@linux.intel.com>
[not found] ` <47dbff997b734d14ada16705068c475e@quantatw.com>
[not found] ` <8139d4fc-3ce8-e753-c000-db713f3e6a2d@linux.intel.com>
[not found] ` <0d4048d2cf1b4dda89179a89b2a624e2@quantatw.com>
[not found] ` <dc07bda4-f926-1b8f-a157-1b0ecfc59e33@linux.intel.com>
2019-03-29 11:00 ` Some questions about "Add option for SEL commands for Journal-based SEL entries" Will Liang (梁永鉉)
2019-03-29 18:14 ` Bills, Jason M [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=6ba86d1a-ecfa-20a8-9b84-8e855fabf320@linux.intel.com \
--to=jason.m.bills@linux.intel.com \
--cc=Buddy.Huang@quantatw.com \
--cc=George.Hung@quantatw.com \
--cc=Richard.Tung@quantatw.com \
--cc=Will.Liang@quantatw.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.