[jinchen62]

Fix KeyError: 'MFMA_BF16_1K' when building install.sh

[Copilot]

Pull request overview

This PR addresses install-time build failures caused by missing optional kernel fields (notably MFMA_BF16_1K) by making access more defensive, and extends custom-kernel naming support via an additional CustomKernelName field.

Changes:

• Avoid KeyError: 'MFMA_BF16_1K' by switching to guarded access when checking BF16_1K MFMA capability.
• Add CustomKernelName as an additional source of kernel/solution names and file base names.
• Treat CustomKernelName as indicating a “custom kernel config” in isCustomKernelConfig.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
projects/hipblaslt/tensilelite/Tensile/SolutionStructs/Naming.py	Adds CustomKernelName fallback for solution/kernel naming and file base generation.
projects/hipblaslt/tensilelite/Tensile/KernelWriter.py	Prevents KeyError by using kernel.get("MFMA_BF16_1K") during MI capability checks.
projects/hipblaslt/tensilelite/Tensile/CustomKernels.py	Expands custom-kernel detection to consider CustomKernelName.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

isCustomKernelConfig now returns True when CustomKernelName is set, but multiple call sites assume True implies config["CustomKernel"]["name"] exists (e.g. Tensile/TensileLogic/HandleCustomKernel.py:52 immediately indexes sol["CustomKernel"]["name"]). With this change, configs that only set CustomKernelName will trigger a KeyError/TypeError downstream.

Suggested fix: either (1) keep isCustomKernelConfig strictly tied to the presence of CustomKernel.name, or (2) update downstream code to consistently derive the name via config.get("CustomKernelName") or config.get("CustomKernel", {}).get("name") and, if needed, populate config["CustomKernel"]["name"] when only CustomKernelName is provided.

Suggested change

	if "CustomKernel" in config and config["CustomKernel"]["name"]:
	return True
	return bool(config.get("CustomKernelName", ""))
	customKernel = config.get("CustomKernel", {})
	return bool(customKernel.get("name"))

[Copilot]

This change makes MFMA_BF16_1K optional (kernel.get(...)) to avoid a KeyError. There doesn't appear to be a unit test covering the previously failing case (kernel dict missing MFMA_BF16_1K). Adding a regression test that exercises kernel generation with a minimal kernel config lacking this key would help prevent future reintroductions.