Uh oh!
There was an error while loading. Please reload this page.
Generalize quantization APIs for FP8/FP4/.. recipes - #2256
Conversation
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 10, 2025
/te-ci pytorch |
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 13, 2025
/te-ci L0 L1 L2 L3 |
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 13, 2025
/te-ci L0 L1 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ksivaman
commented
Oct 13, 2025
For the thunder CI failure: Lightning-AI/lightning-thunder#2635 |
ksivaman
commented
Oct 13, 2025
/te-ci L0 L1 |
Uh oh!
There was an error while loading. Please reload this page.
timmoon10
left a comment
There was a problem hiding this comment.
I don't see any blocking issues, but there are still some minor improvements we could make. Better to put the effort in now to get things exactly right, and there's less risk we'll need to make changes in the future.
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 14, 2025
/te-ci L0 L1 |
| def is_fp8_available() -> Tuple[bool, str]: | ||
| def is_fp8_available(return_reason: bool = False) -> Union[bool, Tuple[bool, str]]: |
There was a problem hiding this comment.
I think this design is a big improvement, especially since if is_fp8_available(): ... does what you expect and since the pattern is consistent between recipes. I do get some code smells from the variable return type. The alternative would be to expose check_fp8_support in the public API and use that when we want reason strings, but that also means expanding the functions we are committing to maintain. I don't have a strong opinion on which approach is better.
There was a problem hiding this comment.
Yeah I went with lower public maintenance while still having the option to do return reason.
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 14, 2025
/te-ci L0 L1 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Tim Moon <4406448+timmoon10@users.noreply.github.com>
timmoon10
commented
Oct 14, 2025
/te-ci L0 L1 |
Signed-off-by: Kirthi Shankar Sivamani <ksivamani@nvidia.com>
ksivaman
commented
Oct 14, 2025
/te-ci L0 L1 |
Description
#2177 and #2254 add support for the NVFP4 recipe. This PR is a follow-up to generalize the user-facing APIs to be agnostic of the recipe dtype and deprecate the old functions/arguments that explicitly mention FP8.
Type of change
Changes
fp8_autocast→autocastfor PyTorch and Jax.fp8_model_init→quantized_model_initfor PyTorch.make_graphed_callablesfor more general versions.is_fp8_available). This PR starts off the process but will likely not be exhaustive. We want to expose as many necessary utils as possible so that users are discouraged to utilize internal TE functionality.Checklist: