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: Wed, 22 Jul 2020 23:21:54 +0530 [thread overview]
Message-ID: <20200722175154.GA23254@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.
Thanks Patrick.
Our platfrom is also based on hot-pluggable multi-host(four) card in chassis.
we have either four host in slots or 2 host with two device card hardware topology.
As you mentioned above on multi-process , Do we need to start and stop each instance based
on host present in the slot at start-up and runtime.
For example if only 2 host connected in slot with other slots empty, do we need to start only 2 instance
and stop the instance when corresponding host card removed from slot at run time.
I understand that you are refering the same design implemented in x86-power-control
and obmc-console for multi-host..
>
> --
> Patrick Williams
next prev parent reply other threads:[~2020-07-22 17:52 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 [this message]
2020-08-04 5:18 ` Manikandan
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=20200722175154.GA23254@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.