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

[Intel GPU] Docs of XPUInductorQuantizer #3293

Open
wants to merge 41 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
19a568a
[Intel GPU] Docs of XPUInductorQuantizer
ZhiweiYan-96 Mar 18, 2025
6bfa4d7
refine
ZhiweiYan-96 Mar 18, 2025
a8e8d8a
syntax
ZhiweiYan-96 Mar 18, 2025
63a63cc
refine
ZhiweiYan-96 Mar 18, 2025
1b3cf01
refine
xiaolil1 Mar 18, 2025
6a9640a
Add img
xiaolil1 Mar 19, 2025
57985bf
fix path
xiaolil1 Mar 19, 2025
4c4069a
picture layout
xiaolil1 Mar 19, 2025
5a6663a
word spelling
ZhiweiYan-96 Mar 20, 2025
79d56de
Merge branch 'main' into zhiwei/xpu_quant
svekars Mar 21, 2025
6a4f748
description, code change
ZhiweiYan-96 Mar 24, 2025
e7e2275
Mov back to prototype_source
ZhiweiYan-96 Mar 24, 2025
d741cf9
fix bug
ZhiweiYan-96 Mar 24, 2025
9a0f0c7
style, image
ZhiweiYan-96 Mar 24, 2025
aae7c51
Merge branch 'main' into zhiwei/xpu_quant
svekars Mar 25, 2025
3a4ecf4
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
584352c
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
b31cc28
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
a84130e
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
dd328d1
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
83fc829
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
4a158d9
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
c209663
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
e95b42b
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
011ef20
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
98ecedc
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
e2d9fbf
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
21a4491
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
204eb89
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
a55cb48
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
046b04f
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
f92a55b
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 1, 2025
384b342
update
ZhiweiYan-96 Apr 1, 2025
6a43ce0
refine
ZhiweiYan-96 Apr 1, 2025
a6516c9
refine
ZhiweiYan-96 Apr 1, 2025
d04de57
Apply suggestions from code review
ZhiweiYan-96 Apr 8, 2025
8e0293a
Update prototype_source/pt2e_quant_xpu_inductor.rst
ZhiweiYan-96 Apr 8, 2025
980079c
fix syntax
ZhiweiYan-96 Apr 8, 2025
640fa94
syntax
ZhiweiYan-96 Apr 8, 2025
17ad15a
refine
ZhiweiYan-96 Apr 8, 2025
41fc5b6
Merge branch 'main' into zhiwei/xpu_quant
svekars Apr 8, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added _static/img/pt2e_quant_xpu_inductor.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 7 additions & 0 deletions prototype_source/prototype_index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,13 @@ Prototype features are not available as part of binary distributions like PyPI o
:link: ../prototype/pt2e_quant_x86_inductor.html
:tags: Quantization

.. customcarditem::
:header: PyTorch 2 Export Quantization with Intel GPU Backend through Inductor

Choose a reason for hiding this comment

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

Intel XPU

Copy link
Author

Choose a reason for hiding this comment

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

At previous stage when we upload RFCs, we recommend using GPU instead of XPU for readability for users. Do we have some changes on this description desicsion?

:card_description: Learn how to use PT2 Export Quantization with Intel GPU Backend through Inductor.
:image: _static/img/thumbnails/cropped/pytorch-logo.png
:link: ../prototype/pt2e_quant_xpu_inductor.html
:tags: Quantization

.. Sparsity

.. customcarditem::
Expand Down
238 changes: 238 additions & 0 deletions prototype_source/pt2e_quant_xpu_inductor.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,238 @@
PyTorch 2 Export Quantization with Intel GPU Backend through Inductor

Choose a reason for hiding this comment

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

Intel XPU

Copy link
Author

Choose a reason for hiding this comment

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

ditto

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
PyTorch 2 Export Quantization with Intel GPU Backend through Inductor
Export Quantization with Intel GPU Backend through Inductor

==================================================================

**Author**: `Yan Zhiwei <https://github.com/ZhiweiYan-96>`_, `Wang Eikan <https://github.com/EikanWang>`_, `Zhang Liangang <https://github.com/liangan1>`_, `Liu River <https://github.com/riverliuintel>`_, `Cui Yifeng <https://github.com/CuiYifeng>`_

Prerequisites
---------------

- `PyTorch 2 Export Post Training Quantization <https://pytorch.org/tutorials/prototype/pt2e_quant_ptq.html>`_
- `TorchInductor and torch.compile concepts in PyTorch <https://pytorch.org/tutorials/intermediate/torch_compile_tutorial.html>`_
- PyTorch 2.7 or later

Introduction
--------------

This tutorial introduces ``XPUInductorQuantizer``, which aims to serve quantized models for inference on Intel GPUs.
``XPUInductorQuantizer`` uses the PyTorch Export Quantization flow and lowers the quantized model into the inductor.

The Pytorch 2 Export Quantization flow uses `torch.export` to capture the model into a graph and perform quantization transformations on top of the ATen graph.
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to call it "PyTorch 2 Export Quantization flow" or can it be just "Export Quantization flow"?

Suggested change
The Pytorch 2 Export Quantization flow uses `torch.export` to capture the model into a graph and perform quantization transformations on top of the ATen graph.
The PyTorch 2 Export Quantization flow uses ``torch.export`` to capture the model into a graph and perform quantization transformations on top of the ATen graph.

Copy link
Author

Choose a reason for hiding this comment

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

hi, @svekars , PyTorch 2 Export here should be a full description of pt2e in APIs like prepare_pt2e, convert_pt2e. Could we keep this just like x86InductorQuantizer here https://pytorch.org/tutorials/prototype/pt2e_quant_x86_inductor.html?

This approach is expected to have significantly higher model coverage with better programmability and a simplified user experience.
TorchInductor is a compiler backend that transforms FX Graphs generated by ``TorchDynamo`` into optimized C++/Triton kernels.

The quantization flow has three steps:

- Step 1: Capture the FX Graph from the eager model based on the `torch export mechanism <https://pytorch.org/docs/main/export.html>`_.
- Step 2: Apply the quantization flow based on the captured FX Graph, including defining the backend-specific quantizer, generating the prepared model with observers,
performing the prepared model's calibration, and converting the prepared model into the quantized model.
- Step 3: Lower the quantized model into inductor with the API ``torch.compile``, which would call Triton kernels or oneDNN GEMM/Convolution kernels.


The high-level architecture of this flow could look like this:

.. image:: ../_static/img/pt2e_quant_xpu_inductor.png

Choose a reason for hiding this comment

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

Please note that Float Model, Example Input and XPUInductorQuantizer is invisible in dark mode.

Copy link
Author

Choose a reason for hiding this comment

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

thanks for reminding, the pictures is moidified

:align: center

Post Training Quantization
----------------------------

Static quantization is the only method we currently support.

The following dependencies are recommended to be installed through the Intel GPU channel:

::

pip3 install torch torchvision torchaudio pytorch-triton-xpu --index-url https://download.pytorch.org/whl/xpu


Please note that since the inductor ``freeze`` feature does not turn on by default yet, you must run your example code with ``TORCHINDUCTOR_FREEZING=1``.

For example:

::

TORCHINDUCTOR_FREEZING=1 python xpu_inductor_quantizer_example.py


1. Capture FX Graph
^^^^^^^^^^^^^^^^^^^^^

We will start by performing the necessary imports, capturing the FX Graph from the eager module.

::

import torch
import torchvision.models as models
from torch.ao.quantization.quantize_pt2e import prepare_pt2e, convert_pt2e
import torch.ao.quantization.quantizer.xpu_inductor_quantizer as xpuiq
from torch.ao.quantization.quantizer.xpu_inductor_quantizer import XPUInductorQuantizer
from torch.export import export_for_training

# Create the Eager Model
model_name = "resnet18"
model = models.__dict__[model_name](weights=models.ResNet18_Weights.DEFAULT)

# Set the model to eval mode
model = model.eval().to("xpu")

# Create the data, using the dummy data here as an example
traced_bs = 50
x = torch.randn(traced_bs, 3, 224, 224, device="xpu").contiguous(memory_format=torch.channels_last)
example_inputs = (x,)

# Capture the FX Graph to be quantized
with torch.no_grad():
exported_model = export_for_training(
model,
example_inputs,
).module()


Next, we will quantize the FX Module.

2. Apply Quantization
^^^^^^^^^^^^^^^^^^^^^^^

After we capture the FX Module, we will import the Backend Quantizer for Intel GPU and configure it to
quantize the model.

::

quantizer = XPUInductorQuantizer()
quantizer.set_global(xpuiq.get_default_xpu_inductor_quantization_config())

The default quantization configuration in ``XPUInductorQuantizer`` uses signed 8-bits for both activations and weights. The tensors are per-tensor quantized, whereas the weights are signed 8-bit per-channel quantized.

Optionally, in addition to the default quantization configuration using asymmetric quantized activation, signed 8-bits symmetric quantized activation is also supported, which has the potential to provide better performance.

::

from torch.ao.quantization.observer import HistogramObserver, PerChannelMinMaxObserver
from torch.ao.quantization.quantizer.quantizer import QuantizationSpec
from torch.ao.quantization.quantizer.xnnpack_quantizer_utils import QuantizationConfig
from typing import Any, Optional, TYPE_CHECKING
if TYPE_CHECKING:
from torch.ao.quantization.qconfig import _ObserverOrFakeQuantizeConstructor
def get_xpu_inductor_symm_quantization_config():
extra_args: dict[str, Any] = {"eps": 2**-12}
act_observer_or_fake_quant_ctr = HistogramObserver
act_quantization_spec = QuantizationSpec(
dtype=torch.int8,
quant_min=-128,
quant_max=127,
qscheme=torch.per_tensor_symmetric, # Change the activation quant config to symmetric
is_dynamic=False,
observer_or_fake_quant_ctr=act_observer_or_fake_quant_ctr.with_args(
**extra_args
),
)

weight_observer_or_fake_quant_ctr: _ObserverOrFakeQuantizeConstructor = (
PerChannelMinMaxObserver
)

weight_quantization_spec = QuantizationSpec(
dtype=torch.int8,
quant_min=-128,
quant_max=127,
qscheme=torch.per_channel_symmetric, # Same as the default config, the only supported option for weight
ch_axis=0, # 0 corresponding to weight shape = (oc, ic, kh, kw) of conv
is_dynamic=False,
observer_or_fake_quant_ctr=weight_observer_or_fake_quant_ctr.with_args(
**extra_args
),
)

bias_quantization_spec = None # will use placeholder observer by default
quantization_config = QuantizationConfig(
act_quantization_spec,
act_quantization_spec,
weight_quantization_spec,
bias_quantization_spec,
False,
)
return quantization_config

# Then, set the quantization configuration to the quantizer.
quantizer = XPUInductorQuantizer()
quantizer.set_global(get_xpu_inductor_symm_quantization_config())

After the backend-specific quantizer is imported, prepare the model for post-training quantization.
``prepare_pt2e`` folds ``BatchNorm`` operators into preceding Conv2d operators, and inserts observers into appropriate places in the model.

::

prepared_model = prepare_pt2e(exported_model, quantizer)

**(For static quantization only)** Calibrate the ``prepared_model`` after the observers are inserted into the model.

::

# We use the dummy data as an example here
prepared_model(*example_inputs)

# Alternatively: user can define the dataset to calibrate
# def calibrate(model, data_loader):
# model.eval()
# with torch.no_grad():
# for image, target in data_loader:
# model(image)
# calibrate(prepared_model, data_loader_test) # run calibration on sample data

Finally, convert the calibrated model to a quantized model. ``convert_pt2e`` takes a calibrated model and produces a quantized model.

::

converted_model = convert_pt2e(prepared_model)

After these steps, the quantization flow has been completed and the quantized model is available.


3. Lower into Inductor
^^^^^^^^^^^^^^^^^^^^^^^^

The quantized model will then be lowered into the inductor backend.

::

with torch.no_grad():
optimized_model = torch.compile(converted_model)

# Running some benchmark
optimized_model(*example_inputs)

In a more advanced scenario, int8-mixed-bf16 quantization comes into play. In this instance,
a convolution or GEMM operator produces the output in BFloat16 instead of Float32 in the absence

Choose a reason for hiding this comment

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

Suggested change
a convolution or GEMM operator produces the output in BFloat16 instead of Float32 in the absence
a Convolution or GEMM operator produces the output in BFloat16 instead of Float32 in the absence

or

Suggested change
a convolution or GEMM operator produces the output in BFloat16 instead of Float32 in the absence
a Conv or GEMM operator produces the output in BFloat16 instead of Float32 in the absence

Copy link
Author

Choose a reason for hiding this comment

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

Thanks for suggestion. We may keep this as here is a vanilla noun.

of a subsequent quantization node. Subsequently, the BFloat16 tensor seamlessly propagates through
subsequent pointwise operators, effectively minimizing memory usage and potentially enhancing performance.
The utilization of this feature mirrors that of regular BFloat16 Autocast, as simple as wrapping the
script within the BFloat16 Autocast context.

::

with torch.amp.autocast(device_type="xpu", dtype=torch.bfloat16), torch.no_grad():
# Turn on Autocast to use int8-mixed-bf16 quantization. After lowering into indcutor backend,
# For operators such as QConvolution and QLinear:
# * The input data type is consistently defined as int8, attributable to the presence of a pair
# of quantization and dequantization nodes inserted at the input.
# * The computation precision remains at int8.
# * The output data type may vary, being either int8 or BFloat16, contingent on the presence
# of a pair of quantization and dequantization nodes at the output.
# For non-quantizable pointwise operators, the data type will be inherited from the previous node,
# potentially resulting in a data type of BFloat16 in this scenario.
# For quantizable pointwise operators such as QMaxpool2D, it continues to operate with the int8
# data type for both input and output.
optimized_model = torch.compile(converted_model)

# Running some benchmark
optimized_model(*example_inputs)


Conclusion
------------

In this tutorial, we have learned how to utilize the ``XPUInductorQuantizer`` to perform post-training quantization on models for inference
on Intel GPUs, leveraging PyTorch 2's Export Quantization flow. We covered the step-by-step process of capturing an FX Graph,
applying quantization, and lowering the quantized model into the inductor backend using ``torch.compile``. Additionally, we explored
the benefits of using int8-mixed-bf16 quantization for improved memory efficiency and potential performance gains,
especially when using ``BFloat16`` autocast.
Loading