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

enable initial build for rocm for fp6_llm #1

Merged

Conversation

lcskrishna
Copy link
Collaborator

@lcskrishna lcskrishna commented Oct 16, 2024

Initial enablement task for FP6_llm.

}
if use_cuda and not IS_ROCM:
Copy link
Owner

Choose a reason for hiding this comment

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

What would be the compile flags for rocm?

@@ -107,17 +108,35 @@ def get_extensions():
extensions_cuda_dir = os.path.join(extensions_dir, "cuda")
cuda_sources = list(glob.glob(os.path.join(extensions_cuda_dir, "**/*.cu"), recursive=True))

if use_cuda:
extensions_hip_dir = os.path.join(extensions_dir, "cuda", "fp6_llm")
hip_sources = list(glob.glob(os.path.join(extensions_hip_dir, "*.cu"), recursive=True))
Copy link
Owner

@petrex petrex Oct 16, 2024

Choose a reason for hiding this comment

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

seems fine for now, but we might have other extensions other than ".cu" later?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes, once we enable all the extensions - we can remove hip_sources and start using cuda_sources directly.

if IS_ROCM and use_cuda:
sources += hip_sources

## TODO: remove this condition and use what we have in CUDA once we fix the individual builds.
Copy link
Owner

Choose a reason for hiding this comment

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

understand we are wip, might be able to consolidate the code later?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes

@petrex
Copy link
Owner

petrex commented Oct 16, 2024

One other question: what would be the entry point for hipify_torch?

@petrex
Copy link
Owner

petrex commented Oct 16, 2024

also I've created an staging branch for this PR : rocm_enablement_staging , let's keep main sync with upstream?

@lcskrishna lcskrishna changed the base branch from main to rocm_enablement_staging October 17, 2024 06:00
@lcskrishna
Copy link
Collaborator Author

also I've created an staging branch for this PR : rocm_enablement_staging , let's keep main sync with upstream?

Updated the PR to use rocm_enablement_staging. That's a good idea to use main for syncing with upstream.

@lcskrishna
Copy link
Collaborator Author

One other question: what would be the entry point for hipify_torch?

Entry points are CUDAExtension. Torch code has integrated hipify_torch as part of CUDAExtensions.

@petrex petrex merged commit 14b3fce into petrex:rocm_enablement_staging Oct 17, 2024
5 of 22 checks passed
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.

2 participants