<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<p style="font-family:Arial;font-size:10pt;color:#0000FF;margin:5pt;font-style:normal;font-weight:normal;text-decoration:none;" align="Left">
[AMD Official Use Only - General]<br>
</p>
<br>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hi Dhanasekar,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is supported for EPYC Genoa family and beyond at this time.<o:p></o:p></p>
<p class="MsoNormal">Daytona uses EPYC Milan family and support is not there in that.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Supreeth Venkatesh</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">System Manageability Architect |<b> AMD</b><br>
Server Software<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"><img width="150" height="35" style="width:1.5625in;height:.3645in" id="Picture_x0020_11" src="cid:image001.png@01D9BBB2.3DA7CC00"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> J Dhanasekar <jdhanasekar@velankanigroup.com> <br>
<b>Sent:</b> Friday, July 21, 2023 5:30 AM<br>
<b>To:</b> Venkatesh, Supreeth <Supreeth.Venkatesh@amd.com><br>
<b>Cc:</b> Zane Shelley <zshelle@imap.linux.ibm.com>; Lei Yu <yulei.sh@bytedance.com>; Michael Shen <gpgpgp@google.com>; openbmc <openbmc@lists.ozlabs.org>; dhruvaraj S <dhruvaraj@gmail.com>; Brad Bishop <bradleyb@fuzziesquirrel.com>; Ed Tanous <ed@tanous.net>;
Dhandapani, Abinaya <Abinaya.Dhandapani@amd.com><br>
<b>Subject:</b> Re: [RFC] BMC RAS Feature<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="background:#FFB900;padding:5.0pt 2.0pt 5.0pt 2.0pt"></td>
<td width="100%" style="width:100.0%;background:#FFF8E5;padding:5.0pt 4.0pt 5.0pt 12.0pt">
<div>
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="color:#222222">Caution:</span></b><span style="color:#222222"> This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Hi Supreeth Venkatesh,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#222222">Does this RAS feature work for the Daytona Platform. i have been working in openBMC development for the Daytonax platform. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#222222">If this RAS works for Daytona Platform. I will include it in my project. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#222222"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#222222">Please provide your suggestions. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Dhanasekar<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="Zm-_Id_-Sgn">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #CCCCCC 1.0pt;padding:0in 0in 0in 0in;margin-top:7.5pt;margin-bottom:7.5pt">
<p class="MsoNormal" style="mso-line-height-alt:0pt"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="Zm-_Id_-Sgn1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">---- On Mon, 03 Apr 2023 22:06:24 +0530
<b>Supreeth Venkatesh <<a href="mailto:supreeth.venkatesh@amd.com">supreeth.venkatesh@amd.com</a>></b> wrote ---<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<blockquote id="blockquote_zmail">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
On 3/23/23 13:57, Zane Shelley wrote: <br>
> Caution: This message originated from an External Source. Use proper <br>
> caution when opening attachments, clicking links, or responding. <br>
> <br>
> <br>
> On 2023-03-22 19:07, Supreeth Venkatesh wrote: <br>
>> On 3/22/23 02:10, Lei Yu wrote: <br>
>>> Caution: This message originated from an External Source. Use proper <br>
>>> caution when opening attachments, clicking links, or responding. <br>
>>> <br>
>>> <br>
>>>>> On Tue, 21 Mar 2023 at 20:38, Supreeth Venkatesh <br>
>>>>> <<a href="mailto:supreeth.venkatesh@amd.com" target="_blank">supreeth.venkatesh@amd.com</a>> wrote:
<br>
>>>>> <br>
>>>>> <br>
>>>>> On 3/21/23 05:40, Patrick Williams wrote: <br>
>>>>> > On Tue, Mar 21, 2023 at 12:14:45AM -0500, Supreeth Venkatesh <br>
>>>>> wrote: <br>
>>>>> > <br>
>>>>> >> #### Alternatives Considered <br>
>>>>> >> <br>
>>>>> >> In-band mechanisms using System Management Mode (SMM) <br>
>>>>> exists. <br>
>>>>> >> <br>
>>>>> >> However, out of band method to gather RAS data is processor <br>
>>>>> specific. <br>
>>>>> >> <br>
>>>>> > How does this compare with existing implementations in <br>
>>>>> > phosphor-debug-collector. <br>
>>>>> Thanks for your feedback. See below. <br>
>>>>> > I believe there was some attempt to extend <br>
>>>>> > P-D-C previously to handle Intel's crashdump behavior. <br>
>>>>> Intel's crashdump interface uses com.intel.crashdump. <br>
>>>>> We have implemented com.amd.crashdump based on that reference. <br>
>>>>> However, <br>
>>>>> can this be made generic? <br>
>>>>> <br>
>>>>> PoC below: <br>
>>>>> <br>
>>>>> busctl tree com.amd.crashdump <br>
>>>>> <br>
>>>>> └─/com <br>
>>>>> └─/com/amd <br>
>>>>> └─/com/amd/crashdump <br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/0
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/1
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/2
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/3
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/4
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/5
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/6
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/7
<br>
>>>>> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">├</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">─</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">/com/amd/crashdump/8
<br>
>>>>> └─/com/amd/crashdump/9 <br>
>>>>> <br>
>>>>> > The repository <br>
>>>>> > currently handles IBM's processors, I think, or maybe that is <br>
>>>>> covered by <br>
>>>>> > openpower-debug-collector. <br>
>>>>> > <br>
>>>>> > In any case, I think you should look at the existing D-Bus <br>
>>>>> interfaces <br>
>>>>> > (and associated Redfish implementation) of these repositories <br>
>>>>> and <br>
>>>>> > determine if you can use those approaches (or document why <br>
>>>>> now). <br>
>>>>> I could not find an existing D-Bus interface for RAS in <br>
>>>>> xyz/openbmc_project/. <br>
>>>>> It would be helpful if you could point me to it. <br>
>>>>> <br>
>>>>> <br>
>>>>> There is an interface for the dumps generated from the host, which <br>
>>>>> can <br>
>>>>> be used for these kinds of dumps <br>
>>>>> <a href="https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml" target="_blank">
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml</a>
<br>
>>>>> <br>
>>>>> <br>
>>>>> The fault log also provides similar dumps <br>
>>>>> <a href="https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml" target="_blank">
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml</a>
<br>
>>>>> <br>
>>>>> <br>
>>>> ThanksDdhruvraj. The interface looks useful for the purpose. However, <br>
>>>> the current BMCWEB implementation references <br>
>>>> <a href="https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/log_services.hpp" target="_blank">
https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/log_services.hpp</a>
<br>
>>>> <br>
>>>> [com.intel.crashdump] <br>
>>>> constexpr char const* crashdumpPath = "/com/intel/crashdump"; <br>
>>>> <br>
>>>> constexpr char const* crashdumpInterface = "com.intel.crashdump"; <br>
>>>> constexpr char const* crashdumpObject = "com.intel.crashdump"; <br>
>>>> <br>
>>>> <a href="https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml" target="_blank">
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml</a>
<br>
>>>> <br>
>>>> or <br>
>>>> <a href="https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml" target="_blank">
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml</a>
<br>
>>>> <br>
>>>> is it exercised in Redfish logservices? <br>
>>> In our practice, a plugin `tools/dreport.d/plugins.d/acddump` is added <br>
>>> to copy the crashdump json file to the dump tarball. <br>
>>> The crashdump tool (Intel or AMD) could trigger a dump after the <br>
>>> crashdump is completed, and then we could get a dump entry containing <br>
>>> the crashdump. <br>
>> Thanks Lei Yu for your input. We are using Redfish to retrieve the <br>
>> CPER binary file which can then be passed through a plugin/script for <br>
>> detailed analysis. <br>
>> In any case irrespective of whichever Dbus interface we use, we need a <br>
>> repository which will gather data from AMD processor via APML as per <br>
>> AMD design. <br>
>> APML <br>
>> Spec: <a href="https://www.amd.com/system/files/TechDocs/57019-A0-PUB_3.00.zip" target="_blank">
https://www.amd.com/system/files/TechDocs/57019-A0-PUB_3.00.zip</a> <br>
>> Can someone please help create bmc-ras or amd-debug-collector <br>
>> repository as there are instances of openpower-debug-collector <br>
>> repository used for Open Power systems? <br>
>>> <br>
>>> <br>
>>> -- <br>
>>> BRs, <br>
>>> Lei YU <br>
> I am interested in possibly standardizing some of this. IBM POWER has <br>
> several related components. openpower-hw-diags is a service that will <br>
> listen for the hardware interrupts via a GPIO pin. When an error is <br>
> detected, it will use openpower-libhei to query hardware registers to <br>
> determine what happened. Based on that information openpower-hw-diags <br>
> will generate a PEL, which is an extended log in phosphor-logging, that <br>
> is used to tell service what to replace if necessary. Afterward, <br>
> openpower-hw-diags will initiate openpower-debug-collector, which <br>
> gathers a significant amount of data from the hardware for additional <br>
> debug when necessary. I wrote openpower-libhei to be fairly agnostic. It <br>
> uses data files (currently XML, but moving to JSON) to define register <br>
> addresses and rules for isolation. openpower-hw-diags is fairly POWER <br>
> specific, but I can see some parts can be made generic. Dhruv would have <br>
> to help with openpower-debug-collector. <br>
Thank you. Lets collaborate in standardizing some aspects of it. <br>
> <br>
> Regarding creation of a new repository, I think we'll need to have some <br>
> more collaboration to determine the scope before creating it. It <br>
> certainly sounds like we are doing similar things, but we need to <br>
> determine if enough can be abstracted to make it worth our time. <br>
I have put in a request here: <br>
<a href="https://github.com/openbmc/technical-oversight-forum/issues/24" target="_blank">https://github.com/openbmc/technical-oversight-forum/issues/24</a>
<br>
Please chime in. <o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>