<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body> <div class="moz-cite-prefix">Kent,<br> <br> What is the command which fails?<br> I can try to duplicate it here.<br> <br> So far, things I've tried, I cannot make rocm-smi fail. Command arguments?<br> <br> Regards,<br> Luben<br> <br> On 2021-10-18 21:06, Russell, Kent wrote:<br> </div> <blockquote type="cite" cite="mid:DM6PR12MB3324C490C0CF191F6F34602C85BD9@DM6PR12MB3324.namprd12.prod.outlook.com"> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 15"> <meta name="Originator" content="Microsoft Word 15"> <link rel="File-List" href="cid:filelist.xml@01D7C463.FB79F840"> <link rel="Edit-Time-Data" href="cid:editdata.mso">  <style>@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-536869121 1107305727 33554432 0 415 0;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-469750017 -1073732485 9 0 511 0;}p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}a:link, span.MsoHyperlink {mso-style-noshow:yes; mso-style-priority:99; color:#0563C1; text-decoration:underline; text-underline:single;}a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; text-decoration:underline; text-underline:single;}p.msonormal0, li.msonormal0, div.msonormal0 {mso-style-name:msonormal; mso-style-unhide:no; margin:0in; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}p.xmsonormal, li.xmsonormal, div.xmsonormal {mso-style-name:x_msonormal; mso-style-unhide:no; margin:0in; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}p.xmsipheadera4477989, li.xmsipheadera4477989, div.xmsipheadera4477989 {mso-style-name:x_msipheadera4477989; mso-style-unhide:no; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault {mso-style-name:x_msochpdefault; mso-style-unhide:no; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}p.msipheader9f8d35bc, li.msipheader9f8d35bc, div.msipheader9f8d35bc {mso-style-name:msipheader9f8d35bc; mso-style-unhide:no; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;}span.xmsohyperlink {mso-style-name:x_msohyperlink; mso-style-unhide:no; color:#0563C1; text-decoration:underline; text-underline:single;}span.xemailstyle18 {mso-style-name:x_emailstyle18; mso-style-unhide:no; font-family:"Calibri",sans-serif; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; mso-bidi-font-family:Calibri; color:windowtext;}span.EmailStyle24 {mso-style-type:personal; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri",sans-serif; mso-ascii-font-family:Calibri; mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri; mso-bidi-font-family:"Times New Roman"; color:windowtext;}span.EmailStyle25 {mso-style-type:personal-reply; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri",sans-serif; mso-ascii-font-family:Calibri; mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri; mso-bidi-font-family:"Times New Roman"; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;}div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> <p class="msipheader9f8d35bc" style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">[AMD Official Use Only]</span><o:p></o:p></p> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman""><o:p> </o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman"">The * is required for the rocm-smi’s functionality for showing what the current clocks are. We had a bug before where the * was removed, then the SMI died fantastically. Work could be done to try to handle that type of situation, but the SMI has a “show current clocks” and uses the * to determine which one is active<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman""><o:p> </o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman"">Kent<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman""><o:p> </o:p></span></p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <p class="MsoNormal"><b><span style="mso-fareast-font-family:"Times New Roman"">From:</span></b><span style="mso-fareast-font-family:"Times New Roman""> amd-gfx <a class="moz-txt-link-rfc2396E" href="mailto:amd-gfx-bounces@lists.freedesktop.org"><amd-gfx-bounces@lists.freedesktop.org></a> <b>On Behalf Of </b>Russell, Kent<br> <b>Sent:</b> Monday, October 18, 2021 9:05 PM<br> <b>To:</b> Tuikov, Luben <a class="moz-txt-link-rfc2396E" href="mailto:Luben.Tuikov@amd.com"><Luben.Tuikov@amd.com></a>; Deucher, Alexander <a class="moz-txt-link-rfc2396E" href="mailto:Alexander.Deucher@amd.com"><Alexander.Deucher@amd.com></a>; Quan, Evan <a class="moz-txt-link-rfc2396E" href="mailto:Evan.Quan@amd.com"><Evan.Quan@amd.com></a>; Lazar, Lijo <a class="moz-txt-link-rfc2396E" href="mailto:Lijo.Lazar@amd.com"><Lijo.Lazar@amd.com></a>; <a class="moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br> <b>Cc:</b> Kasiviswanathan, Harish <a class="moz-txt-link-rfc2396E" href="mailto:Harish.Kasiviswanathan@amd.com"><Harish.Kasiviswanathan@amd.com></a><br> <b>Subject:</b> RE: [PATCH 0/5] 0 MHz is not a valid current frequency<o:p></o:p></span></p> </div> </div> <p class="MsoNormal"><o:p> </o:p></p> <p class="msipheader9f8d35bc" style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">[AMD Official Use Only]</span><o:p></o:p></p> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman""><o:p> </o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman"">+Harish, rocm-smi falls under his purview now.<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman""><o:p> </o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman"">Kent<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-bidi-font-family:"Times New Roman""><o:p> </o:p></span></p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <p class="MsoNormal" style="mso-outline-level:1"><b><span style="mso-fareast-font-family:"Times New Roman"">From:</span></b><span style="mso-fareast-font-family:"Times New Roman""> Tuikov, Luben <<a href="mailto:Luben.Tuikov@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Luben.Tuikov@amd.com</a>> <br> <b>Sent:</b> Monday, October 18, 2021 4:30 PM<br> <b>To:</b> Deucher, Alexander <<a href="mailto:Alexander.Deucher@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Alexander.Deucher@amd.com</a>>; Quan, Evan <<a href="mailto:Evan.Quan@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Evan.Quan@amd.com</a>>; Lazar, Lijo <<a href="mailto:Lijo.Lazar@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Lijo.Lazar@amd.com</a>>; <a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true" class="moz-txt-link-freetext">amd-gfx@lists.freedesktop.org</a>; Russell, Kent <<a href="mailto:Kent.Russell@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Kent.Russell@amd.com</a>><br> <b>Subject:</b> Re: [PATCH 0/5] 0 MHz is not a valid current frequency<o:p></o:p></span></p> </div> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman"">I think Kent is already seen these patches as he did comment on 1/5 patch.<br> <br> The v3 version of the patch, posted last week, removes the asterisk to report the lowest frequency as the current frequency, when the current frequency is 0, i.e. when the block is in low power state. Does the tool rely on the asterisk? If this information is necessary could it not use amdgpu_pm_info?<br> <br> Regards,<br> Luben<br> <br> On 2021-10-18 16:19, Deucher, Alexander wrote:<o:p></o:p></span></p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <p style="margin:15.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:green">[Public]<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman""><o:p> </o:p></span></p> <div> <div> <p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-font-family:"Times New Roman";color:black">We the current behavior (0 for clock) already crashes the tool, so I don't think we can really make things worse.<o:p></o:p></span></p> </div> <div> <p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-font-family:"Times New Roman";color:black"><o:p> </o:p></span></p> </div> <div> <p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-font-family:"Times New Roman";color:black">Alex<o:p></o:p></span></p> </div> <div> <p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-font-family:"Times New Roman";color:black"><o:p> </o:p></span></p> </div> <div class="MsoNormal" style="text-align:center" align="center"><span style="mso-fareast-font-family:"Times New Roman""> <hr width="98%" size="1" align="center"> </span></div> <div id="divRplyFwdMsg"> <p class="MsoNormal" style="mso-outline-level:1"><b><span style="mso-fareast-font-family:"Times New Roman";color:black">From:</span></b><span style="mso-fareast-font-family:"Times New Roman";color:black"> Quan, Evan <a href="mailto:Evan.Quan@amd.com" moz-do-not-send="true"><Evan.Quan@amd.com></a><br> <b>Sent:</b> Thursday, October 14, 2021 10:25 PM<br> <b>To:</b> Lazar, Lijo <a href="mailto:Lijo.Lazar@amd.com" moz-do-not-send="true"><Lijo.Lazar@amd.com></a>; Tuikov, Luben <a href="mailto:Luben.Tuikov@amd.com" moz-do-not-send="true"><Luben.Tuikov@amd.com></a>; <a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true" class="moz-txt-link-freetext"> amd-gfx@lists.freedesktop.org</a> <a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true"> <amd-gfx@lists.freedesktop.org></a>; Russell, Kent <a href="mailto:Kent.Russell@amd.com" moz-do-not-send="true"> <Kent.Russell@amd.com></a><br> <b>Cc:</b> Deucher, Alexander <a href="mailto:Alexander.Deucher@amd.com" moz-do-not-send="true"><Alexander.Deucher@amd.com></a><br> <b>Subject:</b> RE: [PATCH 0/5] 0 MHz is not a valid current frequency</span><span style="mso-fareast-font-family:"Times New Roman""> <o:p></o:p></span></p> <div> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman""> <o:p></o:p></span></p> </div> </div> <div> <div> <p class="xmsipheadera4477989" style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">[AMD Official Use Only]</span><o:p></o:p></p> <p class="xmsonormal"> <o:p></o:p></p> <p class="xmsonormal">+Kent who maintains the Rocm tool<o:p></o:p></p> <p class="xmsonormal"> <o:p></o:p></p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <p class="xmsonormal" style="mso-outline-level:1"><b>From:</b> amd-gfx <a href="mailto:amd-gfx-bounces@lists.freedesktop.org" moz-do-not-send="true"> <amd-gfx-bounces@lists.freedesktop.org></a> <b>On Behalf Of </b>Lazar, Lijo<br> <b>Sent:</b> Thursday, October 14, 2021 1:07 AM<br> <b>To:</b> Tuikov, Luben <a href="mailto:Luben.Tuikov@amd.com" moz-do-not-send="true"><Luben.Tuikov@amd.com></a>; <a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true" class="moz-txt-link-freetext">amd-gfx@lists.freedesktop.org</a><br> <b>Cc:</b> Deucher, Alexander <a href="mailto:Alexander.Deucher@amd.com" moz-do-not-send="true"><Alexander.Deucher@amd.com></a><br> <b>Subject:</b> Re: [PATCH 0/5] 0 MHz is not a valid current frequency<o:p></o:p></p> </div> </div> <p class="xmsonormal"> <o:p></o:p></p> <p style="margin:5.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">[AMD Official Use Only]</span><o:p></o:p></p> <p class="xmsonormal"> <o:p></o:p></p> <div> <p style="margin:5.0pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">[AMD Official Use Only]</span><o:p></o:p></p> <p class="xmsonormal"> <o:p></o:p></p> <div> <div> <p class="xmsonormal" style="background:white"><span style="color:#212121">>Or maybe just a list without default hint, i.e. no asterisk?</span><o:p></o:p></p> </div> <div> <p class="xmsonormal" style="background:white"><span style="color:#212121"> </span><o:p></o:p></p> </div> <div> <p class="xmsonormal" style="background:white"><span style="color:#212121">I think this is also fine meaning we are having trouble in determining the current frequency or DPM level. Evan/Alex? Don't know if this will crash the tools.</span><o:p></o:p></p> </div> <div id="x_ms-outlook-mobile-signature"> <div> <p class="xmsonormal"> <o:p></o:p></p> </div> <p class="xmsonormal">Thanks,<br> Lijo<o:p></o:p></p> </div> <div class="MsoNormal" style="text-align:center" align="center"><span style="mso-fareast-font-family:"Times New Roman""> <hr width="98%" size="1" align="center"> </span></div> <div id="x_divRplyFwdMsg"> <p class="xmsonormal" style="mso-outline-level:1"><b><span style="color:black">From:</span></b><span style="color:black"> Tuikov, Luben <<a href="mailto:Luben.Tuikov@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Luben.Tuikov@amd.com</a>><br> <b>Sent:</b> Wednesday, October 13, 2021 9:52:09 PM<br> <b>To:</b> Lazar, Lijo <<a href="mailto:Lijo.Lazar@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Lijo.Lazar@amd.com</a>>; <a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true" class="moz-txt-link-freetext">amd-gfx@lists.freedesktop.org</a> <<a href="mailto:amd-gfx@lists.freedesktop.org" moz-do-not-send="true" class="moz-txt-link-freetext">amd-gfx@lists.freedesktop.org</a>><br> <b>Cc:</b> Deucher, Alexander <<a href="mailto:Alexander.Deucher@amd.com" moz-do-not-send="true" class="moz-txt-link-freetext">Alexander.Deucher@amd.com</a>><br> <b>Subject:</b> Re: [PATCH 0/5] 0 MHz is not a valid current frequency</span> <o:p> </o:p></p> <div> <p class="xmsonormal"> <o:p></o:p></p> </div> </div> <div> <div> <p class="xmsonormal" style="margin-bottom:12.0pt">On 2021-10-13 00:14, Lazar, Lijo wrote:<br> ><br> > On 10/13/2021 8:40 AM, Luben Tuikov wrote:<br> >> Some ASIC support low-power functionality for the whole ASIC or just<br> >> an IP block. When in such low-power mode, some sysfs interfaces would<br> >> report a frequency of 0, e.g.,<br> >><br> >> $cat /sys/class/drm/card0/device/pp_dpm_sclk<br> >> 0: 500Mhz<br> >> 1: 0Mhz *<br> >> 2: 2200Mhz<br> >> $_<br> >><br> >> An operating frequency of 0 MHz doesn't make sense, and this interface<br> >> is designed to report only operating clock frequencies, i.e. non-zero,<br> >> and possibly the current one.<br> >><br> >> When in this low-power state, round to the smallest<br> >> operating frequency, for this interface, as follows,<br> >><br> > Would rather avoid this -<br> ><br> > 1) It is manipulating FW reported value. If at all there is an uncaught <br> > issue in FW reporting of frequency values, that is masked here.<br> > 2) Otherwise, if 0MHz is described as GFX power gated case, this <br> > provides a convenient interface to check if GFX is power gated.<br> ><br> > If seeing a '0' is not pleasing, consider changing to something like<br> > "NA" - not available (frequency cannot be fetched at the moment).<br> <br> There's a ROCm tool which literally asserts if the values are not ordered in increasing order. Now since 0 < 550, but 0 is listed as the second entry, the tool simply asserts and crashes.<br> <br> It is not clear what you'd rather see here:<br> <br> $cat /sys/class/drm/card0/device/pp_dpm_sclk<br> 0: 550Mhz<br> 1: N/A *<br> 2: 2200MHz<br> $_<br> <br> Is this what you want to see? (That'll crash other tools which expect %uMhz.)<br> <br> Or maybe just a list without default hint, i.e. no asterisk?<br> <br> $cat /sys/class/drm/card0/device/pp_dpm_sclk<br> 0: 550Mhz<br> 1: 2200MHz<br> $_<br> <br> What should the output be?<br> <br> We want to avoid showing 0, but still show numbers.<br> <br> Regards,<br> Luben<br> <br> ><br> > Thanks,<br> > Lijo<br> ><br> >> $cat /sys/class/drm/card0/device/pp_dpm_sclk<br> >> 0: 500Mhz *<br> >> 1: 2200Mhz<br> >> $_<br> >><br> >> Luben Tuikov (5):<br> >> drm/amd/pm: Slight function rename<br> >> drm/amd/pm: Rename cur_value to curr_value<br> >> drm/amd/pm: Rename freq_values --> freq_value<br> >> dpm/amd/pm: Sienna: 0 MHz is not a current clock frequency<br> >> dpm/amd/pm: Navi10: 0 MHz is not a current clock frequency<br> >><br> >> .../gpu/drm/amd/pm/swsmu/smu11/navi10_ppt.c | 60 +++++++++------<br> >> .../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 73 ++++++++++++-------<br> >> 2 files changed, 86 insertions(+), 47 deletions(-)<br> >><o:p></o:p></p> </div> </div> </div> </div> </div> </div> </div> </div> </blockquote> <p class="MsoNormal"><span style="mso-fareast-font-family:"Times New Roman""><o:p> </o:p></span></p> </div> </div> </div> </blockquote> <br> </body> </html>