Skip to content

hw: register vm session's vcpus as trace sources #5793

@skalk

Description

@skalk

Currently, you can observe strange execution times of threads when running x86 virtualization scenarios on top of base-hw. This is due to the fact that only threads and their execution times are collected when using the TRACE session via components like: top or top_view. If a vcpu is using a big share of the cpu time, it is invisible to these tools. Therefore, the relative cpu usage of the residual threads gets over-estimated.
To get appropriated values, and to see the cpu usage of the vcpu, those core objects need to be registered within the global trace source registry.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions