qcom_scm_assign_mem(9)

✨ NAME ✨

okay bestie, meet qcom_scm_assign_mem(9) — this one is from the Kernel API Manual, and it literally makes a secure call to reassign memory ownership. 👑

🌸 SYNOPSIS 🌸

int qcom_scm_assign_mem (phys_addr_t mem_addr , size_t mem_sz , u64
       *srcvm , const struct qcom_scm_vmperm *newvm , unsigned int dest_cnt );

🎀 ARGUMENTS 🎀

• mem_addr — the mem region whose ownership needs to be reassigned. yes, that whole region. 💅
• mem_sz — the size of the region. simple as that.
• srcvm — the vmid for the current set of owners; each set bit in the flag indicates a unique owner. iykyk. ✨
• newvm — an array having the new owners and their corresponding permission flags. new owners, new vibe. 🦋
• dest_cnt — the number of owners in the next set. count ’em. 🔢

🦋 DESCRIPTION 🦋

so basically: it returns a negative errno on failure, or 0 on success with srcvm updated. that’s the whole mood. no cap. 💖

💜 SEE ALSO 💜

the kernel file is ./drivers/firmware/qcom/qcom_scm.c, and the related references are:

• struct qcom_scm_qseecom_resp(9)
• qcom_scm_call(9)
• qcom_scm_call_atomic(9)
• qcom_scm_set_warm_boot_addr(9)
• qcom_scm_set_cold_boot_addr(9)
• qcom_scm_cpu_power_down(9)
• qcom_scm_is_pas_available(9)
• qcom_scm_restore_sec_cfg_available(9)
• qcom_scm_ocmem_lock_available(9)
• qcom_scm_ocmem_lock(9)
• qcom_scm_ocmem_unlock(9)
• qcom_scm_ice_available(9)
• qcom_scm_ice_invalidate_key(9)
• qcom_scm_ice_set_key(9)
• qcom_scm_derive_sw_secret(9)
• qcom_scm_generate_ice_key(9)
• qcom_scm_prepare_ice_key(9)
• qcom_scm_import_ice_key(9)
• qcom_scm_hdcp_available(9)
• qcom_scm_hdcp_req(9)
• qcom_scm_qseecom_call(9)
• qcom_scm_qseecom_get_version(9)
• qcom_scm_qseecom_app_get_id(9)
• qcom_scm_qseecom_app_send(9)
• qcom_scm_qtee_invoke_smc(9)
• qcom_scm_qtee_callback_response(9)
• qcom_scm_is_available(9)

and for the cute lil’ sign-off: this page’s source/version line points to ./drivers/firmware/qcom, dated October 2026, and the footer wraps back to qcom_scm_assign_mem(9). slay. 🫶🎀