Skip to content

Conversation

@nashif
Copy link
Member

@nashif nashif commented Oct 18, 2025

Move cpu_load to lib/os, as this functionality on its own does not
justify being a subsystem on its own.

Fixes #95498

Signed-off-by: Anas Nashif [email protected]

@nashif nashif force-pushed the topic/cpu_load/lib branch from dd548cd to ce39c54 Compare October 18, 2025 11:12
Move cpu_load to lib/os, as this functionality on its own does not
justify being a subsystem on its own.

Fixes zephyrproject-rtos#95498

Signed-off-by: Anas Nashif <[email protected]>
@nashif nashif force-pushed the topic/cpu_load/lib branch from ce39c54 to 46f9ed9 Compare October 18, 2025 11:13
@sonarqubecloud
Copy link

@seankyer
Copy link
Member

seankyer commented Oct 18, 2025

I did create #95498 with the idea that we could create a "metrics subsystem" holding system metrics which could include load, slack, temperature, etc. but didn't get around to it yet.

This metrics directory and its varying kconfigs could live in lib. So like lib/os/metric/cpu_load. But that probably only makes sense to do when we have multiple metrics to handle.

@seankyer
Copy link
Member

Were you able to remove the cpu_load from debug? Or is it not so trivial?

@nashif
Copy link
Member Author

nashif commented Oct 21, 2025

Were you able to remove the cpu_load from debug? Or is it not so trivial?

#97845

@kartben kartben merged commit 24e094e into zephyrproject-rtos:main Oct 22, 2025
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consolidate CPU Load measurement into 'Metrics' type subsystem/kernel service

6 participants