[Kernel] Fix conflicting macro names for gguf kernels

[SzymonOzog]

Just realized that the names for MoE macros are conflicting with MMQ ones at

vllm/csrc/quantization/gguf/mmq.cuh

Line 112 in 4f044b1

#define MMQ_Y_Q4_0 32

Not an issue at the moment because they are the same but might cause bugs in the future

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[Isotr0py]

LGTM!

I think we should separate the MoE kernel out from gguf_kernel.cu to a gguf_moe_kernel.cu and tight it to the moe extension. So that it would be much easier to maintain the GGUF kernel. (In fact, I'm planning an update for GGUF kernel to catchup the MMA support in llama.cpp, but haven't had enough bandwidth to do it yet)

Anyway, we can leave that to be done in a following PR.

[SzymonOzog]

Great! I've also started reading the MMA kernels from llama.cpp and will try to adapt MoE