arm_cca_atte...ion_continue(9)

💅 arm_cca_attestation_continue 💅

okay so this is a page from the Kernel API Manual, bestie — we're in kernel-land today, put your cute little seatbelt on 🎀

---

✨ NAME ✨

arm_cca_attestation_continue — literally just retrieves the attestation token data 🫶

---

🌸 SYNOPSIS 🌸

unsigned long arm_cca_attestation_continue (struct arm_cca_token_info *info );

like... that's the whole vibe. one function, one arg, go off 👑

---

🦋 ARGUMENTS 🦋

• info — a pointer to the arm_cca_token_info. that's it, that's the tea 💖

---

🔥 DESCRIPTION 🔥

okay so here's the thing, and this is so important: attestation token generation is a long running operation 😭 it's giving marathon, not sprint. so the token data may not be retrieved in a single call. not me expecting it to be one-and-done 🙈

and it gets more specific, bestie — the token retrieval operation must be requested on the same CPU on which the attestation token generation was initialised. same CPU. no cap. no switching, no hopping around, none of that 💀

so because of that, this helper function must be executed on that same CPU, multiple times, until the entire token data is retrieved. multiple times!! until the whole thing is home 🏠✨ like a little loop of loyalty, iykyk.

ngl this is the part where people mess up: different CPU = not it. keep it on the same one, periodt.

---

🌈 SEE ALSO 🌈

• the kernel file ./drivers/virt/coco/arm-cca-guest/arm-cca-guest.c 📁
• struct arm_cca_token_info(9)
• arm_cca_report_new(9)
• arm_cca_guest_init(9)
• arm_cca_guest_exit(9)

the whole friend group, honestly 🫶💜

---

and that's the page, bestie 🧚 from ./drivers/virt/coco/arm-cca-guest, dated October 2026 — slay, iconic, ate, no crumbs ⭐💅