[Hardware][CPU] Support AWQ for CPU backend

[bigPYJ1151]

This PR added a new ipex_quant configuration to support various weight-only quantization method with IPEX for the CPU backend.

AWQ is supported for now, a basic test is included.

PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

• [Bugfix] for bug fixes.
• [CI/Build] for build or continuous integration improvements.
• [Doc] for documentation fixes and improvements.
• [Model] for adding a new model or improving an existing model. Model name should appear in the title.
• [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
• [Kernel] for changes affecting CUDA kernels or other compute kernels.
• [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
• [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
• [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

• We adhere to Google Python style guide and Google C++ style guide.
• Pass all linter checks. Please use format.sh to format your code.
• The code need to be well-documented to ensure future contributors can easily understand the code.
• Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
• Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

• After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
• After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
• After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
• Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which consists a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of default ones by unblocking the steps in your fast-check build on Buildkite UI.

Once the PR is approved and ready to go, please make sure to run full CI as it is required to merge (or just use auto-merge).

To run full CI, you can do one of these:

• Comment /ready on the PR
• Add ready label to the PR
• Enable auto-merge.

🚀

[robertgshaw2-neuralmagic]

Thanks!

[bigPYJ1151]

Hi @mgoin , would you please help to review this PR? Because I added a platform filter in awq_marlin compatibility checking. Thanks! :)

[mgoin]

Is there a more informative value that could be used here?

[bigPYJ1151]

This argument is defined as int for now. I added a dict mapping to make it more informative. (AWQ=1, GPTQ=2)

[mgoin]

Can you describe these settings? It seems like this may be quantizing activations as well?

[bigPYJ1151]

Yes, the lowp_mode means the compute type, using int8 for FMA instructions with better performance. The activation is dynamic per-token quantized to int8 with the setting PER_BATCH.

[bigPYJ1151]

Hi @mgoin , do you have any further comments about this? I think this PR is ready to go :)

BTW, seems the CPU CI on the main branch is broken due to a new MOE model test and the lack of the AZP epilogue. I disabled the compressed-tensor test and will fix it recently.

[mgoin]

This looks to be in a good place now, thanks! I just have a nit on UX @bigPYJ1151
Please let me know if I can assist with the compressed-tensors test as we will want to enable that again.

[mgoin]

Could you put a try-catch around the ipex import to provide a better instructive error message to the user? It is also important to enforce versioning if needed.
Something like this deepspeed backend

vllm/vllm/model_executor/layers/quantization/deepspeedfp.py

Lines 144 to 153 in 151ef4e

	try:
	import deepspeed
	if deepspeed.__version__ < "0.14.2":
	raise ImportError("deepspeed version is wrong. Please "
	"install deepspeed>=0.14.2.")
	from deepspeed.ops.fp_quantizer import FP_Quantize
	except ImportError as err:
	raise ImportError("Please install deepspeed>=0.14.2 via "
	"`pip install deepspeed>=0.14.2` to use "
	"deepspeedfp quantizer.") from err