base_asce_alloc(9)
π base_asce_alloc(9) π
okay bestie, this is the Kernel API Manual entry for base_asce_alloc. It's giving very specific kernel-mapping energy, and we're gonna get through it together π
β¨
πΈ NAME πΈ
base_asce_alloc β create kernel mapping without enhanced DAT features
π¦ SYNOPSIS π¦
unsigned long base_asce_alloc (unsigned long addr , unsigned long
num_pages );
π ARGUMENTS π
addrβ virtual start address of kernel mappingnum_pagesβ number of consecutive pages
β¨ DESCRIPTION β¨
So base_asce_alloc generates an asce, including all required region, segment and page tables, that can be used to access the virtual kernel mapping. The difference? The returned asce does not make use of any enhanced DAT features like e.g. large pages. This is required for some I/O functions that pass an asce, like e.g. some service call requests. No cap, that's the assignment π«Ά
β οΈ NOTE β οΈ
Bestie, be so fr: the returned asce may NEVER be attached to any cpu. It may only be used for I/O requests. tlb entries that might result because the asce was attached to a cpu won't be cleared. That is not a vibe β do not do it ππ₯
π₯ SEE ALSO π₯
- Kernel file
./arch/s390/mm/pgalloc.c base_asce_free(9)
mwah π β footer tea: this page comes from ./arch/s390/mm, dated October 2026. That's the whole sign-off, bestie ππ¦
π¦ 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