cpacf_kmc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ cpacf_kmc β€” the one that runs KMC

okay so this is a page from the Kernel API Manual (yes, the cpacf_kmc(9) one, section 9, we're in kernel-land bestie) and it's literally about the KMC instruction β€” that's CIPHER MESSAGE WITH CHAINING for those of us keeping score πŸŽ€


✨ NAME ✨

cpacf_kmc β€” runs the KMC instruction, aka CIPHER MESSAGE WITH CHAINING. That's the whole vibe. πŸ’…


🌸 SYNOPSIS 🌸

int cpacf_kmc (unsigned long func , void *param , u8 *dest , const u8
*src , long src_len );

no cap, that's the signature. five things go in, an int comes out. πŸ¦‹


🧚 ARGUMENTS 🧚

  • func β€” the function code you hand over to KM; peep the CPACF_KMC_xxx defines for what's on the menu πŸ”₯
  • param β€” address of the parameter block; the POP has the deets on what each func actually wants in there πŸ‘‘
  • dest β€” address of the destination memory area (where the good stuff lands) πŸ’–
  • src β€” address of the source memory area (where the good stuff comes from) 🌸
  • src_len β€” length of the src operand, in bytes. bytes!! that's the unit!! ⭐

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: it returns 0 for the query func, and the number of processed bytes for the encryption/decryption funcs. that's it, that's the whole return situation. slay. ✨

iykyk: query func ➑️ 0. encrypt/decrypt func ➑️ processed byte count. don't mix them up bestie 😭

🌈 SEE ALSO 🌈

like a whole friend group of cpacf functions. the whole squad fr fr 🫢


and that's the page!! this cutie lives in ./arch/s390/include/asm, dated October 2026, and it goes by cpacf_kmc(9) β€” go read the whole fam, mwah πŸ’‹πŸ“

πŸ“¦ where this page comes from