Update Jenkinsfile regarding the execution of SPIR-V with the OpenCL and Intel LevelZero runtimes #453
Conversation
This file contains 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
Added the flag to switch the dispatcher and runtime implementation when SPIR-V is going to be tested in Jenkins.
jjfumero
approved these changes
Jun 18, 2024
mairooni
approved these changes
Jun 19, 2024
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.
Description
This PR adds the new flag
-Dtornado.spirv.dispatcherto select the runtime for running SPIR-V generated code, we have to add this option in our JenkinsfileProblem description
As it was getting the "OpenCL" runtime was being selected even if the Level Zero device was explicitly added. The device id are taken from the Jenkins pipeline:
Number of Tornado drivers: 3 [2024-06-17T15:38:47.423Z] Driver: SPIR-V [2024-06-17T15:38:47.423Z] Total number of SPIR-V devices : 2 [2024-06-17T15:38:47.423Z] Tornado device=0:0 (DEFAULT) [2024-06-17T15:38:47.423Z] SPIRV -- SPIRV OCL - Intel(R) UHD Graphics 630 [2024-06-17T15:38:47.423Z] Global Memory Size: 58.5 GB [2024-06-17T15:38:47.423Z] Local Memory Size: 64.0 KB [2024-06-17T15:38:47.423Z] Workgroup Dimensions: 3 [2024-06-17T15:38:47.423Z] Total Number of Block Threads: [256] [2024-06-17T15:38:47.423Z] Max WorkGroup Configuration: [256, 256, 256] [2024-06-17T15:38:47.423Z] Device OpenCL C version: OpenCL C 1.2 [2024-06-17T15:38:47.423Z] [2024-06-17T15:38:47.423Z] Tornado device=0:1 [2024-06-17T15:38:47.423Z] SPIRV -- SPIRV LevelZero - Intel(R) UHD Graphics 630 [2024-06-17T15:38:47.423Z] Global Memory Size: 58.5 GB [2024-06-17T15:38:47.423Z] Local Memory Size: 64.0 KB [2024-06-17T15:38:47.423Z] Workgroup Dimensions: 3 [2024-06-17T15:38:47.423Z] Total Number of Block Threads: [256] [2024-06-17T15:38:47.423Z] Max WorkGroup Configuration: [256, 256, 256] [2024-06-17T15:38:47.423Z] Device OpenCL C version: (LEVEL ZERO) 1.3But when the second device
0:1is selected it takes again the OpenCL runtime:Backend/s tested
Mark the backends affected by this PR.
OS tested
Mark the OS where this PR is tested.
Did you check on FPGAs?
If it is applicable, check your changes on FPGAs.
How to test the new patch?
To reproduce please try the same instructions as Jenkins:
make BACKEND=ptx,opencl,spirv tornado-test --verbose -J"-Dtornado.ptx.priority=100 -Dtornado.unittests.device=1:1 -Dtornado.spirv.dispatcher=levelzero -Dtornado.device.memory=1MB"