[OV][ITT][CPU Plugin] Align ITT markers to standard convention and add async support #33312
Merged
aobolensk merged 3 commits intoopenvinotoolkit:masterfrom Jan 21, 2026
Merged
Conversation
+ Use the same convention standardized in PR#33311 + Ensures the namespace for CPU Plugin activity falls under: ov::phases::inference ov::phases::cpu::inference ov::op::cpu::exec ov::op::cpu::details Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
+ The value of ov:op::cpu::details won't be understood until the graph model mapping between the input model and the optimized execution model requirements are finalized. Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
aobolensk
reviewed
Dec 23, 2025
Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
Contributor
|
build_jenkins |
aobolensk
approved these changes
Jan 19, 2026
praasz
approved these changes
Jan 20, 2026
Merged
via the queue into
openvinotoolkit:master
with commit Jan 21, 2026
967e454
215 of 219 checks passed
Naseer-010
pushed a commit
to Naseer-010/openvino
that referenced
this pull request
Feb 18, 2026
…d async support (openvinotoolkit#33312) Standardizing CPU ITT marker + support for asynchronous execution - Part 2 This PR is the second of a series of PRs to standardize the ITT markers in OpenVINO that will be enabled by default through host-side instrumentation. 1. The first PR addresses the enhancements required in ITT and the framework to support the creation and propagation of IDs when asynchronous execution is in play [PR#33639](openvinotoolkit#33639). 2. This ***second PR*** will standardize ITT markers in the CPU and enhance support to include asynchronous execution. 3. The third PR will enable default markers for GPU plugin to allow visibility into inference pass begin/end and operator preparation and submission within each inference. 4. The final PR will extend the same host side markers for NPU execution, which capturing the inference span and pipeline activity. Summary of the current PR (PR#2) + Use the same convention standardized in [PR#33639](openvinotoolkit#33639) + Ensures the namespace for CPU Plugin activity falls under: - ov::phases::inference - ov::phases::cpu::inference - ov::op::cpu::exec - ov::op::cpu::details Details: CPU support with default enabled ITT markers was limited to synchronous execution. This PR enhances the default support to include asynchronous behavior and ensures a standardized convention is followed in namespaces used. @aobolensk Please review as this is an enhancement of your work with synchronous execution. See [CVS-179230](https://jira.devtools.intel.com/browse/CVS-179230) benchmark data for smoke tests that include low-latency models. --------- Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 19, 2026
… submission (#33313) - Enables default ITT markers for higher level operations such as inference pass, op preparation and submission - Follows the same guidelines to standardize the conventions for namespaces: ov::phases::gpu::inference ov::op::gpu - Supports both synchronous and asynchronous operations Enabling default GPU ITT markers using standard convention - Part 3 This PR is the **third** of a series of PRs to standardize the ITT markers in OpenVINO that will be enabled by default through host-side instrumentation. 1. The first PR addresses the enhancements required in ITT and the framework to support the creation and propagation of IDs when asynchronous execution is in play [PR#33639](#33639). 2. The second PR will standardize ITT markers in the CPU and enhance support to include asynchronous execution [PR#33312](#33312). 3. This **third** PR will enable default markers for GPU plugin to allow visibility into inference pass begin/end and operator preparation and submission within each inference. Follow standardized conventions as described in 1 and 2 4. The final PR will extend the same host side markers for NPU execution, which capturing the inference span and pipeline activity. Summary of the current PR (PR#3) Use the same convention standardized in [PR#33639](#33639) Ensures the namespace for GPU Plugin activity falls under: ov::phases::gpu::inference ov::op::gpu Details: GPU support is enabled with default ITT markers that support synchronous an asynchronous execution. This PR ensures a standardized convention is followed in namespaces used. Tickets: [CVS-179230](https://jira.devtools.intel.com/browse/CVS-179230) @isanghao Please review this as you are generally aware of what was discussed --------- Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 20, 2026
… submission (#33313) - Enables default ITT markers for higher level operations such as inference pass, op preparation and submission - Follows the same guidelines to standardize the conventions for namespaces: ov::phases::gpu::inference ov::op::gpu - Supports both synchronous and asynchronous operations Enabling default GPU ITT markers using standard convention - Part 3 This PR is the **third** of a series of PRs to standardize the ITT markers in OpenVINO that will be enabled by default through host-side instrumentation. 1. The first PR addresses the enhancements required in ITT and the framework to support the creation and propagation of IDs when asynchronous execution is in play [PR#33639](#33639). 2. The second PR will standardize ITT markers in the CPU and enhance support to include asynchronous execution [PR#33312](#33312). 3. This **third** PR will enable default markers for GPU plugin to allow visibility into inference pass begin/end and operator preparation and submission within each inference. Follow standardized conventions as described in 1 and 2 4. The final PR will extend the same host side markers for NPU execution, which capturing the inference span and pipeline activity. Summary of the current PR (PR#3) Use the same convention standardized in [PR#33639](#33639) Ensures the namespace for GPU Plugin activity falls under: ov::phases::gpu::inference ov::op::gpu Details: GPU support is enabled with default ITT markers that support synchronous an asynchronous execution. This PR ensures a standardized convention is followed in namespaces used. Tickets: [CVS-179230](https://jira.devtools.intel.com/browse/CVS-179230) @isanghao Please review this as you are generally aware of what was discussed --------- Signed-off-by: Vasanth Tovinkere <vasanth.tovinkere@intel.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standardizing CPU ITT marker + support for asynchronous execution - Part 2
This PR is the second of a series of PRs to standardize the ITT markers in OpenVINO that will be enabled by default through host-side instrumentation.
Summary of the current PR (PR#2)
Details:
CPU support with default enabled ITT markers was limited to synchronous execution. This PR enhances the default support to include asynchronous behavior and ensures a standardized convention is followed in namespaces used.
@aobolensk Please review as this is an enhancement of your work with synchronous execution.
See CVS-179230 benchmark data for smoke tests that include low-latency models.