Skip to content

Auxiliary devices in SOF break check-ipc-flood.sh (IPC3) #467

Closed

Description

@xiulipan

Auxiliary devices in SOF thesofproject/linux#2501 break check-ipc-flood.sh https://sof-ci.01.org/sofpr/PR3545/build7503/devicetest/

quick check find big change in debugfs

/sys/kernel/debug/sof# ls
cc_version  debug  dsp  etrace  exception  filter  fw_version  hda  inbox  outbox  pp  probes  regs  snd_sof_client.ipc_test.0  snd_sof_client.ipc_test.1  stream  trace
/sys/kernel/debug/sof# ls snd_sof_client.ipc_test.*
snd_sof_client.ipc_test.0:
ipc_flood_count  ipc_flood_duration_ms

snd_sof_client.ipc_test.1:
ipc_flood_count  ipc_flood_duration_ms

Activity

  1. xiulipan commented on Oct 23, 2020

    @xiulipan
    ContributorAuthor

    @ranj063 could you give more info about the change here.

  2. fredoh9 commented on Oct 23, 2020

    @fredoh9
    Contributor

    The IPC debugfs will be moved to IPC client. And by default we have two IPC test clients.
    Easy solution is chaging path to first client, snd_sof_client.ipc_test.0

    /sys/kernel/debug/sof/snd_sof_client.ipc_test.0/ipc_flood_count
    echo "10000" > /sys/kernel/debug/sof/snd_sof_client.ipc_test.0/ipc_flood_count
    

    And we need to update the test case with multiple IPC clients. Or we can add new IPC test case for this also.

    # write to two ipc test client simultaneously
    echo "10000" > /sys/kernel/debug/sof/snd_sof_client.ipc_test.0/ipc_flood_count &
    echo "10000" > /sys/kernel/debug/sof/snd_sof_client.ipc_test.1/ipc_flood_count
    
  3. xiulipan commented on Oct 26, 2020

    @xiulipan
    ContributorAuthor

    @fredoh9 Will the path always be look like this? eg: snd_sof_client.ipc_test.*/ipc_flood_count
    PS: if we have only one client, what will those debugfs be look like?

  4. ranj063 commented on Oct 26, 2020

    @ranj063
    Contributor

    @fredoh9 Will the path always be look like this? eg: snd_sof_client.ipc_test.*/ipc_flood_count
    PS: if we have only one client, what will those debugfs be look like?

    Yes. if there's only one then, you'd only see snd_sof_client.ipc_test.0

  5. added
    type:enhancementNew framework feature or request
    P3Low-impact bugs or features
    on Jan 26, 2021
  6. marc-hb commented on Aug 13, 2024

    @marc-hb
    Collaborator

    I think we will never test flood with IPC4, correct?

    If correct please close as wontfix

  7. plbossart commented on Aug 13, 2024

    @plbossart
    Member

    I don't know what prevents us from flooding the firmware with IPCs, regardless of the IPC type.

    @ujfalusi would you agree?

  8. ujfalusi commented on Aug 13, 2024

    @ujfalusi
    Contributor

    Nothing prevents us from flooding the firmware, but the flood test uses a special test IPC3 message (SOF_IPC_GLB_TEST_MSG | SOF_IPC_TEST_IPC_FLOOD), this is not present for IPC4.
    I don't think this is going to be supported.

    Is this really broken today for IPC3? The PR that this issue is blaming had never been merged, the sof-client infra ended up with different implementation...
    Yes, you need to build the client module and make sure that it is loaded, but it should be working (for IPC3, it is not going to probe with IPC4).

  9. changed the title [-]Auxiliary devices in SOF break check-ipc-flood.sh[/-] [+]Auxiliary devices in SOF break check-ipc-flood.sh (IPC3)[/+] on Aug 13, 2024
  10. marc-hb commented on Aug 13, 2024

    @marc-hb
    Collaborator

    Thank you for the clarifications!

    IPC3 flooding has been working just fine https://sof-ci.ostc.intel.com/#/result/planresultdetail/44673

    IPC4 flooding is currently skipped with the somewhat misleading "need debug firmware".
    https://sof-ci.ostc.intel.com/#/result/planresultdetail/44691
    There is another ticket about IPC4+flood specifically, I mixed it up with this one a bit, sorry about that: #1066
    I'll see if can quickly make this message better.

    The PR that this issue is blaming had never been merged, the sof-client infra ended up with different implementation...

    Great, so we can definitely close this ticket, these will never be resurrected somehow? Also, #191 looks like a duplicate? Close that too? It points at thesofproject/linux#1841 instead of 2501. All part of the same, dead thing?

  11. fredoh9 commented on Aug 14, 2024

    @fredoh9
    Contributor

    IPC flood test is not applicable to IPC4 at this moment, this is not breaking any test case any more.
    How to support IPC flood test is different story/topic.

  12. fredoh9 commented on Aug 14, 2024

    @fredoh9
    Contributor

    Oh, this is about IPC3. Anyway we can still close this as this is not the case any more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P3Low-impact bugs or featuresstate:ping-for-closeWill be closed if submitter is not responsivetype:enhancementNew framework feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions