kvm_s390_upd...hange_report(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ kvm_s390_upd...hange_report(9) ✨

okay so bestie, buckle up β€” we're in the Kernel API Manual today (yes, the Kernel API Manual, we're fancy now πŸ’…) and this page is about kvm_s390_update_topology_change_report. i know, i know, the title in the header got cut off like kvm_s390_upd...hange_report(9) β€” that's just the man page being dramatic and truncating, don't panic 🫢


🌸 NAME 🌸

kvm_s390_update_topology_change_report β€” update CPU topology change report

like. it updates the report. about topology changes. for CPUs. iconic behavior honestly ✨


πŸŽ€ SYNOPSIS πŸŽ€

void kvm_s390_update_topology_change_report (struct kvm *kvm , bool val );

that's the whole thing!! void return, two args, no cap πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • kvm β€” the guest KVM description. literally the whole vibe of the guest, hand it over please 🫢
  • val β€” set or clear the MTCR bit. yes it's just a bool deciding whether we're setting or clearing, main character energy fr πŸ”₯

🌈 DESCRIPTION 🌈

okay so what this does: it updates the Multiprocessor Topology-Change-Report bit, and the whole point is to signal the guest that a topology change happened. like a little "hey girl, something moved πŸ‘€" nudge to the guest.

but β€” and this is important, bestie β€” it's only relevant if the topology facility is present. no facility, no relevance. that's the vibe check and it passed (or didn't, depending on the facility) πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

kernal file ./arch/s390/kvm/s390/s390.c β€” go read it, it's giving source material ✨

and the whole friend group of related functions:

they all show up together, it's a whole squad πŸ«ΆπŸ’œ


and that's the page!! shoutout to the source/version tag ./arch/s390/kvm/s390 and the date October 2026 β€” that's the cute little sign-off at the bottom, mwah πŸ’‹ see u next man page bestie πŸŽ€β­

πŸ“¦ where this page comes from