All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manikandan <manikandan.hcl.ers.epl@gmail.com>
To: openbmc@lists.ozlabs.org
Cc: kuiying.wang@intel.com, manikandan.e@hcl.com, velumanit@hcl.com
Subject: add multi-host support in the phosphor-post-code-manager
Date: Mon, 20 Jul 2020 21:30:13 +0530	[thread overview]
Message-ID: <20200720160013.GB17117@cnn> (raw)

Hi All,

 We woukld like to get opion on below multi-host support approaches.

Background :
------------
  The Phosphor-post-code-manager supports only host 
to store/retrieve the host postcode history.

Approaches:
-----------
Approach 1: << run the multiple process >>

Create and run the multiple phosphor-post-code-manager process to handle each host postcode history.

   xyz.openbmc_project.State.Host0.Boot.PostCode
   xyz.openbmc_project.State.Host1.Boot.PostCode
   xyz.openbmc_project.State.Host2.Boot.PostCode
   xyz.openbmc_project.State.Host3.Boot.PostCode

Approach 2: << pass number of host to single process >>

Pass number of host to single process phosphor-post-code-manager to register dbus object 
and handle each host postcode.

   xyz.openbmc_project.State.Host0.Boot.PostCode
   xyz.openbmc_project.State.Host1.Boot.PostCode
   xyz.openbmc_project.State.Host2.Boot.PostCode
   xyz.openbmc_project.State.Host3.Boot.PostCode


Thanks
Mani.E

             reply	other threads:[~2020-07-20 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 16:00 Manikandan [this message]
2020-07-21 15:20 ` add multi-host support in the phosphor-post-code-manager Patrick Williams
2020-07-22 17:51   ` Manikandan
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=20200720160013.GB17117@cnn \
    --to=manikandan.hcl.ers.epl@gmail.com \
    --cc=kuiying.wang@intel.com \
    --cc=manikandan.e@hcl.com \
    --cc=openbmc@lists.ozlabs.org \
    --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.