zfcp_qdio_siosl(9)
π zfcp_qdio_siosl
okay so bestie, welcome to the Kernel API Manual β¨ this one's a tiny little function with main character energy β it's giving "small but crucial," no cap π
π NAME π
zfcp_qdio_siosl β trigger logging in the FCP channel π₯
β¨ SYNOPSIS β¨
void zfcp_qdio_siosl (struct zfcp_adapter *adapter );
like, that's it. that's the whole call. iconic π«Ά
π¦ ARGUMENTS π¦
adapterβ thezfcp_adapterwhere you wanna trigger the logging π« literally just tell it which one, bestie.
πΈ DESCRIPTION πΈ
so here's the vibe: you call the cio siosl function to trigger hardware logging π that's the whole mission.
but wait β this wrapper function also sets a flag so that hardware logging only gets triggered once before going through qdio shutdown π like, one and done, we're not doing reruns, periodt.
and ngl, the triggers are always run from qdio tasklet context, so no additional synchronization is necessary π no locks, no stress, no "who touched what first" drama. the context already handled it for you π
π SEE ALSO π
peep the kernel file ./drivers/s390/scsi/zfcp_qdio.c for the whole friend group π§ and obviously go say hi to:
zfcp_qdio_sbals_from_sg(9)zfcp_qdio_sbal_get(9)zfcp_qdio_send(9)zfcp_qdio_allocate(9)zfcp_qdio_close(9)zfcp_qdio_open(9)
and that's the page, bestie π brought to you by the fine folks over at ./drivers/s390/scsi, dated October 2026, and yeah β it's literally zfcp_qdio_siosl(9) π slay π
β¨
π¦ 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