Fix mixed KV cache: type_v_first used instead of type_v_last for last layers (#1626)

In llama_kv_cache_init() call, params.type_v_first was incorrectly passed
twice instead of params.type_v_last.
This caused V cache in the last N layers to use type_v_first instead of type_v_last.

Fix: Replace second params.type_v_first with params.type_v_last.
This commit is contained in:
Nexes the Elder 2026-04-13 07:23:13 +02:00 committed by GitHub
parent 08ae48c667
commit 67268c8fde
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -5727,7 +5727,7 @@ struct llama_context * llama_init_from_model(
ctx->backends.push_back(ctx->backend_cpu);
if (!llama_kv_cache_init(ctx->kv_self, ctx, type_k, type_v, kv_size, cparams.offload_kqv,
params.type_k_first, params.type_k_last, params.type_v_first, params.type_v_first,
params.type_k_first, params.type_k_last, params.type_v_first, params.type_v_last,
params.n_k_first, params.n_k_last, params.n_v_first, params.n_v_last)) {
LLAMA_LOG_ERROR("%s: llama_kv_cache_init() failed for self-attention cache\n", __func__);
llama_free(ctx);