Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

instruments/trace_cmd: Add tracing mode support to TraceCmdInstrument() #1276

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

metin-arm
Copy link
Contributor

Implement tracing mode support (mainly for write-to-disk mode) in TraceCmdInstrument, enabling efficient collection of large trace datasets without encountering memory limitations.

This feature is particularly useful for scenarios requiring extensive trace data.

Additional changes:

  • Replace hardcoded strings with corresponding string literals for improved maintainability.

Implement tracing mode support (mainly for write-to-disk mode) in
TraceCmdInstrument, enabling efficient collection of large trace
datasets without encountering memory limitations.

This feature is particularly useful for scenarios requiring extensive
trace data.

Additional changes:
- Replace hardcoded strings with corresponding string literals for
  improved maintainability.

Signed-off-by: Metin Kaya <[email protected]>
@douglas-raillard-arm
Copy link
Contributor

douglas-raillard-arm commented Jan 29, 2025

LGTM however it needs to wait until this devlib PR is merged:
ARM-software/devlib#689
And then until a new release of devlib is done on PyPI. At that point, the version bound on devlib for WA will need to be increased to ensure that devlib has that parameter

EDIT: strikethrough

Copy link
Contributor

@marcbonnici marcbonnici left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also looks good to me.

And thanks @douglas-raillard-arm for the poke on the corresponding devlib PR. I think we can avoid having to wait for a PyPi release but you're correct we'll need at least a dev bump to align these PR's when merging.

@douglas-raillard-arm
Copy link
Contributor

douglas-raillard-arm commented Jan 29, 2025

I think we can avoid having to wait for a PyPi release

Just came back to remove that part from my comment. As long as WA's PyPI release is not pushed before devlib's one it's probably ok to only support devlib's master in WA's master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants