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

fix: CTS bugs in Sysman Device module #69

Merged

Conversation

vishnu-khanth
Copy link
Contributor

Related-To: VLCLJ-2272

Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Copy link
Contributor

@harinik124 harinik124 left a comment

Choose a reason for hiding this comment

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

Looks fine.

Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Copy link
Contributor

@pratikbariintel pratikbariintel left a comment

Choose a reason for hiding this comment

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

lgtm !

@vishnu-khanth vishnu-khanth marked this pull request as draft September 12, 2024 11:06
@vishnu-khanth vishnu-khanth marked this pull request as ready for review October 7, 2024 10:58
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
@vishnu-khanth
Copy link
Contributor Author

vishnu-khanth commented Oct 8, 2024

The approach followed :

  1. Add events before and after the launch kernel in command list.
  2. Check for Engine type between those two events.
    • If it's updated, then test passes.
      
    • Else, check for engine type after workload completion with timeout of 10 seconds. If updated within timeout, test passes with a warning message (Workaround)
      

@vishnu-khanth
Copy link
Contributor Author

vishnu-khanth commented Oct 8, 2024

This CTS will be revisited & workaround will be removed once the GetProcessState API is fixed/debugged. With this workaround fix test is passing consistently.

Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
Related-To: VLCLJ-2272

Signed-off-by: Vishnu Khanth <vishnu.khanth.b@intel.com>
@vishnu-khanth
Copy link
Contributor Author

vishnu-khanth commented Oct 16, 2024

FYI, the workaround has been removed.
Now the test is passing consistently in platforms where KMD updates the process state correctly.
Failing consistently in platforms where KMD doesn't update process state correctly.

@AshwinKumarKulkarni AshwinKumarKulkarni merged commit 32527cc into oneapi-src:master Oct 16, 2024
13 checks passed
@vishnu-khanth vishnu-khanth deleted the process_state_cts_fix branch October 17, 2024 06:18
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.

6 participants