Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=linux.vnet.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=zshelle@linux.vnet.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.vnet.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44DQCc2kD0zDqCt for ; Wed, 6 Mar 2019 05:19:40 +1100 (AEDT) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x25IELWE015230 for ; Tue, 5 Mar 2019 13:19:37 -0500 Received: from e11.ny.us.ibm.com (e11.ny.us.ibm.com [129.33.205.201]) by mx0a-001b2d01.pphosted.com with ESMTP id 2r1v84pvg0-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 05 Mar 2019 13:19:37 -0500 Received: from localhost by e11.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 5 Mar 2019 18:19:35 -0000 Received: from b01cxnp22034.gho.pok.ibm.com (9.57.198.24) by e11.ny.us.ibm.com (146.89.104.198) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 5 Mar 2019 18:19:33 -0000 Received: from b01ledav001.gho.pok.ibm.com (b01ledav001.gho.pok.ibm.com [9.57.199.106]) by b01cxnp22034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x25IJXYJ19595286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 5 Mar 2019 18:19:33 GMT Received: from b01ledav001.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0176A28058; Tue, 5 Mar 2019 18:19:33 +0000 (GMT) Received: from b01ledav001.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7CFB52805C; Tue, 5 Mar 2019 18:19:32 +0000 (GMT) Received: from ltc.linux.ibm.com (unknown [9.16.170.189]) by b01ledav001.gho.pok.ibm.com (Postfix) with ESMTP; Tue, 5 Mar 2019 18:19:32 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 05 Mar 2019 12:27:10 -0600 From: zshelle To: openbmc@lists.ozlabs.org Cc: openbmc Subject: Re: New repo for System Fatal Error Diagnostics for POWER Systems In-Reply-To: <8f90bbe93f545017f281fa433b5f3660@linux.vnet.ibm.com> References: <8f90bbe93f545017f281fa433b5f3660@linux.vnet.ibm.com> X-Sender: zshelle@linux.vnet.ibm.com User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 x-cbid: 19030518-2213-0000-0000-0000035E5CE2 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010710; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000281; SDB=6.01170066; UDB=6.00611482; IPR=6.00950699; MB=3.00025843; MTD=3.00000008; XFM=3.00000015; UTC=2019-03-05 18:19:35 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19030518-2214-0000-0000-00005D91F970 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-05_10:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903050120 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: Tue, 05 Mar 2019 18:19:40 -0000 On 2019-02-28 10:38, zshelle wrote: > The design proposal is here: > https://gerrit.openbmc-project.xyz/#/c/openbmc/docs/+/18591/ > > In the design proposal, I indicated we need a repo for the analyzer > side and the isolator side of the diagnostics. The analyzer side will > all be OpenBMC specific code. That is the easy one. The isolator side > will be common code used throughout several projects within OpenPOWER > in addition to its application in OpenBMC. It's been pointed out to me > that there will be some convenient advantages to putting this isolator > repo in the OpenBMC project. However, it will be used heavily in > several OpenPOWER projects. I should point out that while the isolator > is currently geared towards POWER, it has the potential to be used on > other architectures in the future. I would appreciate any input on > this topic. Is there enough information in the proposal to at least get the repos created? Sorry to push, but I want to get these repos created before I am out on paternity leave starting this Friday. For the analyzer, I was thinking of openpower-hw-diags or something along those lines. I could use some suggestions for the isolator. It sounds like it could be used by more than POWER.