From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4864:20::1041; helo=mail-pj1-x1041.google.com; envelope-from=manikandan.hcl.ers.epl@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20161025 header.b=kKZHpBo4; dkim-atps=neutral Received: from mail-pj1-x1041.google.com (mail-pj1-x1041.google.com [IPv6:2607:f8b0:4864:20::1041]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4BBjhj4JfMzDqyJ for ; Thu, 23 Jul 2020 03:52:05 +1000 (AEST) Received: by mail-pj1-x1041.google.com with SMTP id 8so1906086pjj.1 for ; Wed, 22 Jul 2020 10:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=VC6lV5F5+i8HDKqSmPxP1I4p/LgwyLnug16D6d1PVyI=; b=kKZHpBo4CQ+y4LykxD9UMVwxZ+R/k2LEyZwIiK/93zYXHiUEF3wTt3Hj3EEsIuUWy3 vmL6yHpomSw8MvEiXdOZvArfm9Q/fd+NxN4YEPctpe6GXSAsOj7eCJT+SOeWGRNuLUg6 WwxXR5+Zb4vMtgwTRcKJHkjlQ+1MFXZsu5vgcmUAElWKyadJQ3j+WqAhzPm7ozU+hubk eNhYqke69jVpU3o55r4z9tw0s2CTh7G+Rf676Or5+rPzTBf571559YqrSE9I9m7VNSPA tFzIbJ2s/ihyJNNtJ2YnRyHoDOzpvoTxgosN0QWo7wShZ9YvsEqyN/QGn0PxzI6XGjbj FMwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=VC6lV5F5+i8HDKqSmPxP1I4p/LgwyLnug16D6d1PVyI=; b=ARHbHywZqovAPh4631rm9sI3zO0pYzDo1OTzb8cCPUpWFNIzmBsJRAnvETA7NO/94L 5PS7T82l7+Z3VEDsR0ZBqXPOFgFFoe1ObHAR1GhNr3JWBzwJ+oDYJeY/71dSjjttiwwi mqfA5iLSHyrgbBgaxs5wmYGcpFrz4JrgL6TeVKLsANTBigcRKFgsSTKbrJ6j8W/16Bgh 8Mt4uWkv2PBK+KnFQcpdMxyAu5em7FuDWEfTIv7JzNfSf/SpqNVcLUTwQ0O54C9dmhVT SiPk8vkH2IFUqn+hzTNcbwT/klAa4N9H2U2R02F2wN7z0oI0CQN6Uo5tgSpU+D1bA525 kllQ== X-Gm-Message-State: AOAM532Ld51LlXcYBQL832BegRjtOpjmZc6zJNbKR6d3roRjl5bvkNQJ 0rlZLBrNuAZo0pwf56x92Xc= X-Google-Smtp-Source: ABdhPJwe0UbchiujPpnj1rR04T4k8XmsCEapPISPNbWEde+vgatnHHXDaRpZjWDSrXnocLrz1I7UWQ== X-Received: by 2002:a17:90a:2681:: with SMTP id m1mr474245pje.204.1595440321961; Wed, 22 Jul 2020 10:52:01 -0700 (PDT) Received: from cnn ([112.133.236.103]) by smtp.gmail.com with ESMTPSA id 66sm241938pfg.63.2020.07.22.10.51.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2020 10:51:59 -0700 (PDT) Date: Wed, 22 Jul 2020 23:21:54 +0530 From: Manikandan To: Patrick Williams 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 Message-ID: <20200722175154.GA23254@cnn> References: <20200720160013.GB17117@cnn> <20200721152016.GL3922@heinlein> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200721152016.GL3922@heinlein> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2020 17:52:06 -0000 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