Skip to content

[DEV] fix(megatron-fsdp): preserve non-meta tensors during meta device materialization#4155

Open
xuwchen wants to merge 1 commit intoNVIDIA:devfrom
xuwchen:fix_mfsdp_meta_device_init_dev
Open

[DEV] fix(megatron-fsdp): preserve non-meta tensors during meta device materialization#4155
xuwchen wants to merge 1 commit intoNVIDIA:devfrom
xuwchen:fix_mfsdp_meta_device_init_dev

Conversation

@xuwchen
Copy link
Copy Markdown
Contributor

@xuwchen xuwchen commented Apr 6, 2026

main PR: #4154

What does this PR do ?

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

Contribution process

Pre-checks

  • 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

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

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.

@xuwchen xuwchen requested review from a team as code owners April 6, 2026 10:37
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot bot commented Apr 6, 2026

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.

@xuwchen xuwchen requested a review from shjwudp April 7, 2026 02:15
Copy link
Copy Markdown
Contributor

@shjwudp shjwudp left a comment

Choose a reason for hiding this comment

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

Good catch! Some bias parameters are stored as nn.Module buffers (though that’s not a standard PyTorch practice). These buffers weren’t initialized on the meta device and shouldn’t be converted to empty tensors. This PR fixes that issue and also resolves the unexpected NaNs observed in the functional tests with the MoE layer.

for name, param in module.named_parameters(recurse=False):
if param.is_meta:
new = torch.empty_like(param, device=device)
setattr(module, name, torch.nn.Parameter(new, requires_grad=param.requires_grad))
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please do not reconfigures module parameters, which might cause loss of existing attributes on those parameters or invalidate maps that used these parameters as keys.

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