xe_survivabi...is_requested(9)
β¨ NAME β¨
xe_survivability_mode_is_requested β bestie, this is the vibe check that tells you whether survivability mode (the one firmware or userspace was like "hey can we turn this on?") is actually possible to enable π
(also hi, you're reading the xe_survivability_mode_is_requested(9) page, welcome π)
πΈ SYNOPSIS πΈ
bool xe_survivability_mode_is_requested (struct xe_device *xe );
okay so it's a bool. it either slays (true) or it doesn't (false). no in-between, no "it's complicated" π¦
π ARGUMENTS π
xeβ the xe device instance. literally the device we're asking about, that's it, that's the whole arg π«Ά
π§ DESCRIPTION π§
So this function pulls up and reads two things, no cap:
- configfs π
- boot status from Pcode πΎ
that's the whole job. it reads them, and based on what it finds it tells you whether survivability mode is a go or a no-go β¨
π₯ RETURN π₯
Returns true when both of these line up:
- platform support is available β
- the boot status indicates failure π
β¦or if survivability mode is straight-up requested πββοΈ
Otherwise? false. that's it. that's the answer βοΈ
ngl, read that carefully β the "boot status indicates failure" part is doing a lot of work in that sentence and it's not the same thing as just "someone asked for it" π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_survivability_mode.cπ Survivability Mode(9)β the main character of this whole saga πxe_survivability_mode_is_boot_enabled(9)xe_survivability_mode_runtime_enable(9)xe_survivability_mode_boot_enable(9)
and that's the page, bestie πβ¨
sign-off szn: this chaotic little beauty lives under ./drivers/gpu/drm/xe, dated October 2026, and it's filed as xe_survivabi...is_requested(9) in case you were wondering why the title looks like it got cut off mid-sentence β it did, it's giving "typed it too fast in the group chat" ππ
π¦ 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