create_basic_memory_bitmaps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– create_basic_memory_bitmaps(9) β€” the kernel API manual, but make it make sense πŸŽ€

okay so bestie, welcome to the <bold>kernel API manual</bold> ✨ β€” this one's a create_basic_memory_bitmaps(9) situation and honestly? it's a little guy with one job and it does it well. let's get into it 🫢


✨ NAME ✨

create_basic_memory_bitmaps β€” literally just: create bitmaps to hold basic page information. that's the whole vibe πŸ’…


🌸 SYNOPSIS 🌸

int create_basic_memory_bitmaps (void );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” no arguments. nothing. zero. the void is voiding πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

so here's the tea β˜• β€” this function creates the bitmaps you need for two things:

  1. marking page frames that should not be saved
  2. marking free page frames

and the <hotpink>forbidden_pages_map</hotpink> and <hotpink>free_pages_map</hotpink> pointers? they only get modified <bold>if everything goes well</bold> β€” that's not a flex, that's a whole design decision. the reasoning is that we don't` want the bits touched before both bitmaps are set up. like, no cap, both or nothing. all-or-nothing energy. iconic ✨

fr fr β€” the "only if everything goes well" part is the whole point. don't be out here expecting those pointers to move on a failure, because they won't. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

here's the whole friend group 🫢 β€” and btw this all lives in the kernel file <purple>./kernel/power/snapshot.c</purple>:

go read them all, i'll wait πŸ’œ


and that's the page babes 🌈 β€” brought to you by the <mint>./kernel/power</mint> directory, <yellow>October 2026</yellow> edition, still out here explaining create_basic_memory_bitmaps(9) to the masses. slay, stay hydrated, and remember: both bitmaps or nothing πŸ’…πŸ’–πŸŽ€

πŸ“¦ where this page comes from