While handling LARGE_CONFIG_GET->MEMORY_STATE_INFO_GET, SOF FW always reports the total amount of pages (compile time constants) instead of the current usage. Usefulness of this information is limited. It would be nice to have the real data that gets updated after topology load. Benefits:
- Allow HW/Architecture teams to optimize memory (size/provision)
- Allow clients (e.g. Topology designers) to experiment and assess memory footprints of individual components/features
- Check for memory leaks (e.g. reloading topology in a loop and checking the allocation size)
I discovered this gap some time ago. But recently there was an ask about SOF memory footprint. So maybe it's time to properly handle this IPC.