From: James Feist <james.feist@linux.intel.com>
To: Alex Qiu <xqiu@google.com>, Ed Tanous <ed@tanous.net>
Cc: Peter Lundgren <peterlundgren@google.com>,
Benjamin Fair <benjaminfair@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Ofer Yehielli <ofery@google.com>, Josh Lehan <krellan@google.com>,
Richard Hanley <rhanley@google.com>,
Kais Belgaied <belgaied@google.com>
Subject: Re: Feedback on Current OpenBMC and Proposing Some Improvements ---- "Improvements" Ideas
Date: Wed, 8 Jul 2020 10:55:58 -0700 [thread overview]
Message-ID: <17e2960e-eecd-eca8-4c70-ecfdec9e66f5@linux.intel.com> (raw)
In-Reply-To: <CAA_a9xLuCPRGawer58S-XUMo_2A27hLYsn=5_0LE4BUvqSLmtg@mail.gmail.com>
On 7/1/2020 10:06 AM, Alex Qiu wrote:
>>> For the parser, I'm referring to the function templateCharReplace() in
>>> https://github.com/openbmc/entity-manager/blob/master/src/Utils.cpp#L154.
>>> We found it unintuitive that it does not support parenthesis and does
>>> not follow arithmetic order of operations. If we try to improve it to
>>> support parenthesis and arithmetic order of operations, it will break
>>> compatibility if we don't watch it carefully.
A real parser would be a great addition, at the time we had no idea all
of the different replacement functions we would be adding.
>> Yes, it's not a real parser, but if you look at the commit for the
>> problem it was fixing (massively duplicated config files for power
>> supplies because of minor changes) then it starts to make more sense
>> that what's there is better than what came before. If it's important
>> to you, then put together a patch to add a real parser? Remember that
>> the relevant config files are checked into that repo, so you can
>> actually dump every single config statement and flush it through your
>> parser to test that it gives the same result, and in the cases it
>> doesn't, add parenthesis where required to get the same result. I
>> would really only expect the quad mode power supply files to even be
>> effected, and I believe (based on how their expression is parsed) they
>> won't be.
> For the concern of compatibility, we worry that other companies are
> also using these features downstream. FYI, we are heavily relying on
> it right now, even though we find out it's not following arithmetic
> order of operations.
I think that is outside of the projects hands, and should influence
others to upstream their configurations so that they get all necessary
changes/support when new features are added.
next prev parent reply other threads:[~2020-07-08 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:26 Feedback on Current OpenBMC and Proposing Some Improvements ---- "Improvements" Ideas Alex Qiu
2020-06-21 22:16 ` Ed Tanous
2020-06-24 1:30 ` Alex Qiu
2020-06-25 14:43 ` Ed Tanous
2020-06-26 1:08 ` Alex Qiu
2020-06-29 14:53 ` Ed Tanous
2020-06-29 22:09 ` Alex Qiu
2020-06-30 1:28 ` Ed Tanous
2020-06-30 21:28 ` Alex Qiu
2020-07-01 2:00 ` Ed Tanous
2020-07-01 17:06 ` Alex Qiu
2020-07-08 17:55 ` James Feist [this message]
2020-07-08 18:06 ` Ed Tanous
2020-07-08 21:46 ` Alex Qiu
2020-07-09 6:15 ` Ed Tanous
2020-07-09 12:42 ` Brad Bishop
2020-07-09 16:13 ` Alex Qiu
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=17e2960e-eecd-eca8-4c70-ecfdec9e66f5@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=belgaied@google.com \
--cc=benjaminfair@google.com \
--cc=ed@tanous.net \
--cc=krellan@google.com \
--cc=ofery@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=peterlundgren@google.com \
--cc=rhanley@google.com \
--cc=xqiu@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.