From: Manikandan <manikandan.hcl.ers.epl@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: openbmc@lists.ozlabs.org, kuiying.wang@intel.com,
velumanit@hcl.com, manikandan.e@hcl.com
Subject: Re: add multi-host support in the phosphor-post-code-manager
Date: Tue, 4 Aug 2020 10:48:56 +0530 [thread overview]
Message-ID: <20200804051856.GA6678@cnn> (raw)
In-Reply-To: <20200721152016.GL3922@heinlein>
On Tue, Jul 21, 2020 at 10:20:16AM -0500, Patrick Williams wrote:
> On Mon, Jul 20, 2020 at 09:30:13PM +0530, Manikandan wrote:
> > Approach 1: << run the multiple process >>
> >
> > Create and run the multiple phosphor-post-code-manager process to handle each host postcode history.
>
> I would lean towards this implementation because I think it is more
> flexible in the long term. Some multi-host systems are hot-pluggable
> such that you do not statically know how many you're going to have. In
> some cases you have cards that take up two or three slots, so you really
> don't know the correct topology until you've done discovery.
>
Hi Patrick,
our platform also hot-plug-able and supports maximum four host
with different hardware topology. Do we need register and unregister
based on hosts inserted or removed from the slot.
The multi-host support on obmc-console, host-logger and x86-power-control
based on number of host passed from receipe.
I have updated design docuement in below Gerrit and your comments
will helpful regards hot-plug-able host D-Bus creation and deletion.
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/35065
Thanks
Mani.E
> --
> Patrick Williams
next prev parent reply other threads:[~2020-08-04 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 16:00 add multi-host support in the phosphor-post-code-manager Manikandan
2020-07-21 15:20 ` Patrick Williams
2020-07-22 17:51 ` Manikandan
2020-08-04 5:18 ` Manikandan [this message]
2020-07-21 17:10 ` Ren, Zhikui
2020-07-21 18:28 ` Vijay Khemka
2020-07-23 20:31 ` Manikandan
2020-07-24 16:21 ` Manikandan
2020-07-24 16:32 ` Ren, Zhikui
2020-07-27 2:38 ` Wang, Kuiying
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=20200804051856.GA6678@cnn \
--to=manikandan.hcl.ers.epl@gmail.com \
--cc=kuiying.wang@intel.com \
--cc=manikandan.e@hcl.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=velumanit@hcl.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.