STRUCT CMD_BUF_DESC(9)
π struct cmd_buf_desc(9) π
ok so first things first, this is from the Kernel API Manual β yes bestie, the kernel, we're in the big leagues now π«Ά
β¨ NAME β¨
struct cmd_buf_desc β the descriptor squad that manages legacy SEV command address parameters, the ones that point at buffers firmware might write into π
πΈ SYNOPSIS πΈ
struct cmd_buf_desc {
u64 *paddr_ptr;
u64 paddr_orig;
u32 len;
bool guest_owned;
};
π Members π
paddr_ptrβ pointer to the address parameter inside the command buffer, the one that might need saving/restoring depending on whether a bounce buffer is in play π«. When there is a bounce buffer, the command buffer has to get updated with the address of that shiny new bounce buffer thatsnp_map_cmd_buf_descallocated specifically for it, iykyk. Must beNULLif this descriptor is only an end-of-list indicator β no cap, that's the rule πpaddr_origβ storage for the original address parameter π. You use it to restore the original value back intopaddr_ptrwhen it got swapped out for the address of a bounce buffer. literally the save file for your address, periodt.lenβ the length of the buffer sitting at the address originally stored inpaddr_ptrπguest_ownedβtrueif the address maps to guest-owned pages, in which case bounce buffers are not needed π (slay, one less thing).
π¦ SEE ALSO π¦
Kernel file ./drivers/crypto/ccp/sev-dev.c π
ok that's the whole page, you ate that π β¨
source: ./drivers/crypto/ccp β dated October 2026 ππ§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms