You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Auxiliary devices in SOF break check-ipc-flood.sh (IPC3) #467
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
@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?
@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
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).
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
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?
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.
Activity
xiulipan commentedon Oct 23, 2020
@ranj063 could you give more info about the change here.
fredoh9 commentedon Oct 23, 2020
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
And we need to update the test case with multiple IPC clients. Or we can add new IPC test case for this also.
xiulipan commentedon Oct 26, 2020
@fredoh9 Will the path always be look like this? eg:
snd_sof_client.ipc_test.*/ipc_flood_countPS: if we have only one client, what will those debugfs be look like?
ranj063 commentedon Oct 26, 2020
Yes. if there's only one then, you'd only see snd_sof_client.ipc_test.0
marc-hb commentedon Aug 13, 2024
I think we will never test flood with IPC4, correct?
If correct please close as wontfix
plbossart commentedon Aug 13, 2024
I don't know what prevents us from flooding the firmware with IPCs, regardless of the IPC type.
@ujfalusi would you agree?
ujfalusi commentedon Aug 13, 2024
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).
[-]Auxiliary devices in SOF break check-ipc-flood.sh[/-][+]Auxiliary devices in SOF break check-ipc-flood.sh (IPC3)[/+]marc-hb commentedon Aug 13, 2024
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.
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?
fredoh9 commentedon Aug 14, 2024
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.
fredoh9 commentedon Aug 14, 2024
Oh, this is about IPC3. Anyway we can still close this as this is not the case any more.