<div dir="ltr"><div>You found the right threads to follow, and you're right that this is lacking some documentation.  (Patches/Writeups welcome.)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 10:18 AM Mathew Benson <<a href="mailto:mbenson@windhoverlabs.com">mbenson@windhoverlabs.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>"SHED" = scheduler_name, but that traces back to:</div><div>    name.name_u32 = _Thread_Scheduler_get_home( rtems_thread )->name;<br>    _Objects_Name_to_string(<br>      name,<br>      false,<br>      canonical_task->scheduler_name,<br>      sizeof( canonical_task->scheduler_name )<br>    );</div><div><br></div><div>Shelve that one until later...</div><div><br></div><div>"STATE" = state.  That traces back to rtems_monitor_dump_state()... which eventually traces back to:</div><div>static const rtems_assoc_32_pair state_pairs[] = {<br>  { STATES_WAITING_FOR_MUTEX,              "MTX" },<br>  { STATES_WAITING_FOR_SEMAPHORE,          "SEM" },<br>  { STATES_WAITING_FOR_EVENT,              "EV" },<br>  { STATES_WAITING_FOR_SYSTEM_EVENT,       "SYSEV" },<br>  { STATES_WAITING_FOR_MESSAGE,            "MSG" },<br>  { STATES_WAITING_FOR_CONDITION_VARIABLE, "CV" },<br>  { STATES_WAITING_FOR_FUTEX,              "FTX" },<br>  { STATES_WAITING_FOR_BSD_WAKEUP,         "WK" },<br>  { STATES_WAITING_FOR_TIME,               "TIME" },<br>  { STATES_WAITING_FOR_PERIOD,             "PER" },<br>  { STATES_WAITING_FOR_SIGNAL,             "SIG" },<br>  { STATES_WAITING_FOR_BARRIER,            "BAR" },<br>  { STATES_WAITING_FOR_RWLOCK,             "RW" },<br>  { STATES_WAITING_FOR_JOIN_AT_EXIT,       "JATX" },<br>  { STATES_WAITING_FOR_JOIN,               "JOIN" },<br>  { STATES_SUSPENDED,                      "SUSP" },<br>  { STATES_WAITING_FOR_SEGMENT,            "SEG" },<br>  { STATES_LIFE_IS_CHANGING,               "LIFE" },<br>  { STATES_DEBUGGER,                       "DBG" },<br>  { STATES_INTERRUPTIBLE_BY_SIGNAL,        "IS" },<br>  { STATES_WAITING_FOR_RPC_REPLY,          "RPC" },<br>  { STATES_ZOMBIE,                         "ZOMBI" },<br>  { STATES_DORMANT,                        "DORM" }</div><div><br></div><div>modes traces t o rtems_monitor_dump_modes(), which eventually traces to:</div><div>static const rtems_assoc_t rtems_monitor_modes_assoc[] = {<br>    { "nP",     RTEMS_NO_PREEMPT, 0 },<br>    { "T",      RTEMS_TIMESLICE, 0 },<br>    { "nA",     RTEMS_NO_ASR, 0 },<br>    { 0, 0, 0 },<br>};</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 11:07 AM Mathew Benson <<a href="mailto:mbenson@windhoverlabs.com" target="_blank">mbenson@windhoverlabs.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">The task command doesn't appear to be defined there.  I found the header in libmisc/monitor/mon-task.c:rtems_monitor_task_dump_header().  It gets a little buried in function callbacks from there.  I'm trying to trace it back now, but I recommend the documentation be improved to include what the output actually means.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 9:50 AM Jonathan Brandmeyer <<a href="mailto:jbrandmeyer@planetiq.com" target="_blank">jbrandmeyer@planetiq.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">cpukit/libmisc/shell/ has many of the entry points for the shell functions.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 6:39 AM <<a href="mailto:mbenson@windhoverlabs.com" target="_blank">mbenson@windhoverlabs.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">I take it that’s a no on the documentation.  Can somebody just tell me what these mean or point me where in the code it is?  It’s not an easy follow.<br><br><div id="gmail-m_8338224453344934307gmail-m_7845695420780976978gmail-m_2437449986026767864gmail-m_5650052873737614921AppleMailSignature" dir="ltr">Sent from my iPhone</div><div dir="ltr"><br>On Oct 31, 2019, at 13:43, Mathew Benson <<a href="mailto:mbenson@windhoverlabs.com" target="_blank">mbenson@windhoverlabs.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>is there any documentation that explains the actual output of the shell commands?  For example, the documentation for the task command says how to run it, and gives the following sample output:</div><div><br></div><div><pre>SHLL <span>[</span>/<span>]</span> <span># task</span>
ID       NAME                 SHED PRI STATE  MODES    EVENTS WAITINFO
------------------------------------------------------------------------------
0a010001 UI1                  UPD  <span>254</span> EV     P:T:nA   NONE
0a010002 SHLL                 UPD  <span>100</span> READY  P:T:nA   NONE</pre></div><div><br></div><div>But doesn't actually explain what the data in the columns mean.  What do the following "STATE" values mean:  EV, SIG:IS, READY, MSG, SEM, and TIME?  What do the MODES mean?  Same question for the "sema" command output.  <br></div><div><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div><div><b>Mathew Benson</b><br></div>CEO | Chief Engineer<br></div>Windhover Labs, LLC<br>832-640-4018<br><br><img src="https://drive.google.com/a/windhoverlabs.com/uc?id=1cLDczWESrU667xKgEJlFhHa2yjq5UVhJ&export=download"><br></div><a href="http://www.windhoverlabs.com" target="_blank">www.windhoverlabs.com</a><br><br></div></div></div></div></div></div>
</div></blockquote></div>_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr">Jonathan Brandmeyer<br>Vice President of Software Engineering<br>PlanetiQ</div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div><div><b>Mathew Benson</b><br></div>CEO | Chief Engineer<br></div>Windhover Labs, LLC<br>832-640-4018<br><br><img src="https://drive.google.com/a/windhoverlabs.com/uc?id=1cLDczWESrU667xKgEJlFhHa2yjq5UVhJ&export=download"><br></div><a href="http://www.windhoverlabs.com" target="_blank">www.windhoverlabs.com</a><br><br></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div><div><b>Mathew Benson</b><br></div>CEO | Chief Engineer<br></div>Windhover Labs, LLC<br>832-640-4018<br><br><img src="https://drive.google.com/a/windhoverlabs.com/uc?id=1cLDczWESrU667xKgEJlFhHa2yjq5UVhJ&export=download"><br></div><a href="http://www.windhoverlabs.com" target="_blank">www.windhoverlabs.com</a><br><br></div></div></div></div>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a></blockquote></div></div>