scsw_is_valid_dstat(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scsw_is_valid_dstat β€” the scsw filesystem-CSW field-inspector page, from the Kernel API Manual ✨

okay so bestie, welcome to the scsw_is_valid_dstat manual page πŸ’– this one lives over in the Kernel API Manual and it's short, sweet, and honestly kinda iconic for it. we're checking whether one little field is valid. that's the whole vibe. no cap.


🌸 NAME 🌸

scsw_is_valid_dstat β€” check dstat field validity πŸŽ€

✨ SYNOPSIS ✨

int scsw_is_valid_dstat (union scsw *scsw );

🫢 ARGUMENTS 🫢

  • scsw β€” pointer to scsw. that's it, that's the argument. she points, we check πŸ’…

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• this function returns non-zero if the dstat field of the specified scsw is valid β€” and the way it does not care whether it's a transport mode scsw or a command mode scsw is honestly main character energy 🌈 like, valid is valid, periodt.

it returns zero if the field does not contain a valid value πŸ’€ that's the vibe check failing, bestie.

fr fr: non-zero = valid dstat, zero = not valid. both modes welcomed, no gatekeeping πŸ¦‹

πŸ”₯ SEE ALSO πŸ”₯

okay this list is long long, so buckle up 🎒 everything below is a real reference and we're not skipping a single one, iykyk:

  • Kernel file ./arch/s390/include/asm/scsw.h
  • struct cmd_scsw(9), struct tm_scsw(9), struct eadm_scsw(9), union scsw(9)

the field accessors:

the command-mode validity crew:

the transport-mode validity crew:

the mode-agnostic validity crew:

and the solicited squad:


that's the whole page, bestie β€” short and slay πŸ’œ this one's from ./arch/s390/include/asm and it's dated October 2026, so go forth and validate those dstat fields, no cap 🧚⭐

πŸ“¦ where this page comes from