setup_apcb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ setup_apcb(9) ✨

okay so bestie, we're in the Kernel API Manual today and this one is literally about s390 crypto control blocks πŸ’… buckle up πŸŽ€


πŸ’– NAME πŸ’–

setup_apcb β€” Create a shadow copy of the apcb.

like, it makes a shadow copy. a little twin. main character energy for a data structure πŸ¦‹


🌸 SYNOPSIS 🌸

int setup_apcb (struct kvm_vcpu *vcpu , struct kvm_s390_crypto_cb
*crycb_s , const u32 crycb_gpa , struct kvm_s390_crypto_cb *crycb_h ,
int fmt_o , int fmt_h );

that's the whole signature, no cap. six things go in, an int comes out πŸ”₯


🫢 ARGUMENTS 🫢

  • vcpu β€” pointer to the virtual CPU. the little virtual guy we're doing all this for πŸ‘‘
  • crycb_s β€” pointer to shadow crycb. yes bestie, the shadow copy lives here πŸ’œ
  • crycb_gpa β€” guest physical address of original guest crycb. like, the address where the real one is chilling πŸ“
  • crycb_h β€” pointer to the host crycb. the host's own version, iconic πŸ’…
  • fmt_o β€” format of the original guest crycb. just the guest format, don't overthink it πŸ“
  • fmt_h β€” format of the host crycb. and this is the host's format 🌸

🌈 DESCRIPTION 🌈

so what it actually does: it checks the compatibility between the guest and host crycb and calls the appropriate copy function. that's it, that's the vibe check ✨

Return 0 or an error number if the guest and host crycb are incompatible. 😭 like if they don't match, you get an error number back, that's the whole deal. no compatible formats, no shadow copy, periodt πŸ’€


πŸ¦‹ SEE ALSO πŸ¦‹


and that's the page bestie, go read the friends too, iykyk πŸ’–

signing off from ./arch/s390/kvm/s390, October 2026 β€” stay slay, stay compatible β­πŸŽ€

πŸ“¦ where this page comes from