Skip to content

[DEV][NVFP4] Fix NVFP4 Selective Activation Recompute - #2036

Merged
yanring merged 7 commits into
NVIDIA:devfrom
zhongbozhu:zhongbo/fix_nvfp4_act_recomp
Nov 18, 2025
Merged

[DEV][NVFP4] Fix NVFP4 Selective Activation Recompute #2036
yanring merged 7 commits into
NVIDIA:devfrom
zhongbozhu:zhongbo/fix_nvfp4_act_recomp

Conversation

@zhongbozhu

@zhongbozhu zhongbozhu commented Oct 29, 2025

Copy link
Copy Markdown
Contributor

What does this PR do ?

NVFP4 MOE is already available in dev branch, but it has some issues with selective activation recompute because some logic hardcoded FP8. This PR is to fix it.

PR to main branch also has this fix: #1985

This PR also bumps up align size of FP4 to 64 from 32 based on TE PR: NVIDIA/TransformerEngine#2351

Contribution process

flowchart LR
    A[Pre-checks] --> B[PR Tests]
    subgraph Code Review/Approval
        C1[Expert Review] --> C2[Final Review]
    end
    B --> C1
    C2 --> D[Merge]
Loading

Pre-checks

  • I want this PR in a versioned release and have added the appropriate Milestone (e.g., Core 0.8)
  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.

For MRs into `main` branch

(Step 1): Add PR label Expert Review

(Step 2): Collect the expert reviewers reviews

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

(Step 3): Final Review

  1. Add Final Review label
  2. GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.

(Optional Step 4): Cherry-pick into release branch

If this PR also needs to be merged into core_r* release branches, after this PR has been merged, select Cherry-pick to open a new PR into the release branch.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@zhongbozhu
zhongbozhu requested review from a team as code owners October 29, 2025 22:46
@copy-pr-bot

copy-pr-bot Bot commented Oct 29, 2025

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@hxbai
hxbai requested a review from yanring October 30, 2025 00:13
@yanring
yanring enabled auto-merge October 30, 2025 01:18
@yanring

yanring commented Oct 30, 2025

Copy link
Copy Markdown
Contributor

/ok to test a982793

@copy-pr-bot

copy-pr-bot Bot commented Oct 30, 2025

Copy link
Copy Markdown

/ok to test a982793

@yanring, there was an error processing your request: E2

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/2/

@yanring

yanring commented Oct 30, 2025

Copy link
Copy Markdown
Contributor

/ok to test 7598039

@yaox12

yaox12 commented Nov 5, 2025

Copy link
Copy Markdown
Member

/ok to test dc682de

return get_fp8_align_size(config.fp8_recipe)
elif config.fp4:
return get_fp4_align_size(config.fp4_recipe)
return 16

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Maybe change 16 to None for bf16?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This 16 is for other fp8 recipes like per-tensor current scaling.
BF16 shouldn't call this function.

@Victarry Victarry added the dev branch Dev branch related issues and development label Nov 7, 2025
@zhongbozhu

Copy link
Copy Markdown
Contributor Author

Bumping up align size to 64 for future grouped nvfp4 kernels: NVIDIA/TransformerEngine#2351

@yanring

yanring commented Nov 10, 2025

Copy link
Copy Markdown
Contributor

/ok to test de9127b

@yanring
yanring added this pull request to the merge queue Nov 18, 2025
Merged via the queue into NVIDIA:dev with commit 7da6e5b Nov 18, 2025
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dev branch Dev branch related issues and development Final Review PR is in the "final review" stage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants