这是indexloc提供的服务,不要输入任何密码
Skip to content

Use CONCURRENT_KERNEL tracing in KernelNameTracer #97280

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

Merged
merged 1 commit into from
Jul 22, 2025

Conversation

copybara-service[bot]
Copy link

Use CONCURRENT_KERNEL tracing in KernelNameTracer

The standard kernel tracing serializes kernel execution which doesn't play with command buffers. I see different results with command buffers enabled compared to command buffers disabled.

Switching to the concurrent kernel tracing fixes the issue and leads to consistent results.

This is also backfilling the kernel names for B200 in the DotAlgorithm tests.

@copybara-service copybara-service bot force-pushed the exported_pr_785411976 branch from c7e3f87 to f800922 Compare July 21, 2025 14:19
The standard kernel tracing serializes kernel execution which doesn't play with command buffers. I see different results with command buffers enabled compared to command buffers disabled.

Switching to the concurrent kernel tracing fixes the issue and leads to consistent results.

This is also backfilling the kernel names for B200 in the DotAlgorithm tests.

PiperOrigin-RevId: 785731546
@copybara-service copybara-service bot force-pushed the exported_pr_785411976 branch from f800922 to 4ac8ed8 Compare July 22, 2025 07:21
@copybara-service copybara-service bot merged commit 4ac8ed8 into master Jul 22, 2025
@copybara-service copybara-service bot deleted the exported_pr_785411976 branch July 22, 2025 07:21
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.

1 participant