Skip to content

Conversation

@jinz2014
Copy link

@jinz2014 jinz2014 commented Jan 24, 2025

This commit follows the implementation #1796 to support the experimental urKernelSuggestMaxCooperativeGroupCountExp, for the HIP adapter, to retrieve the maximum number of cooperative groups that can be launched on the device.

Additionally, the changes also cache the result of the hipDeviceAttributeMultiprocessorCount query which is used to calculate the device-wide maximum cooperative groups, because the HIP occupancy query used has per multiprocessor semantics.

@jinz2014 jinz2014 requested a review from a team as a code owner January 24, 2025 22:13
@jinz2014 jinz2014 requested a review from ldrumm January 24, 2025 22:13
@jchlanda
Copy link
Contributor

cc @GeorgeWeb

@jchlanda jchlanda requested a review from GeorgeWeb January 27, 2025 08:24
&MaxNumActiveGroupsPerCU, hKernel->get(), localWorkSize,
dynamicSharedMemorySize));
detail::ur::assertion(MaxNumActiveGroupsPerCU >= 0);
// Handle the case where we can't have all SMs active with at least 1 group
Copy link
Contributor

Choose a reason for hiding this comment

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

I think AMD calls these WGPs (Work-Group Processors). SM is for Nvidia architectures.

@github-actions github-actions bot added the hip HIP adapter specific issues label Jan 27, 2025
Copy link
Contributor

@GeorgeWeb GeorgeWeb left a comment

Choose a reason for hiding this comment

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

Could you please describe the changes a little more in the description field of this PR? It is used as part of the final squashed commit's message alongside the title upon merge. Thank you.

@jinz2014
Copy link
Author

jinz2014 commented Feb 3, 2025

@GeorgeWeb
I thought of testing which may be blocking the PR to merge. Could you please let me how tests could be added ?

@martygrant
Copy link
Contributor

Unified Runtime -> intel/llvm Repo Move Notice

Information

The source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory,
all future development will now be carried out there. This was done in intel/llvm#17043.

The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime.

The contribution guide has been updated with new instructions for contributing to Unified Runtime.

PR Migration

All open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days.
To allow for some breathing space, this automation will not be enabled until next week (27/02/2025).

Should you wish to continue with your PR you will need to migrate it to intel/llvm.
We have provided a script to help automate this process.


This is an automated comment.

@martygrant
Copy link
Contributor

Unified Runtime -> intel/llvm Repo Move Notice

Following on from the previous notice, we have now enabled workflows to automatically label and close PRs because the Unified Runtime source code has moved to intel/llvm.

This PR has now been marked with the auto-close label and will be automatically closed after 30 days.

Please review the previous notice for more information, including assistance with migrating your PR to intel/llvm.

Should there be a reason for this PR to remain open, manually remove the auto-close label.


This is an automated comment.

@github-actions
Copy link
Contributor

Automatic PR Closure Notice

Information

This PR has been closed automatically. It was marked with the auto-close label 30 days ago as part of the Unified Runtime source code migration to the intel/llvm repository - intel/llvm#17043.

All Unified Runtime development should be done in intel/llvm, details can be found in the updated contribution guide.
This repository will continue to exist as a mirror and will host the specification documentation.

Next Steps

Should you wish to re-open this PR it must be moved to intel/llvm. We have provided a script to help automate this process, otherwise no actions are required.


This is an automated comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-close hip HIP adapter specific issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants