Constant CPU_PROFILE_LONG_HELP 

pub const CPU_PROFILE_LONG_HELP: &str = "The CPU the guest sees: x86-64-v2 (the default), x86-64-v3, or host-no-rdrand. host-no-rdrand is available for `hermit run` on the ptrace backend with CPUID faulting and virtual time; it refuses hosts without CPUID faulting instead of allowing native CPUID. RDRAND and RDSEED are hidden. Check availability with `hermit host-capabilities --cpu-profile host-no-rdrand`. Recording and replay with host-no-rdrand are not supported.\n\nWith --cpu-profile host-no-rdrand, CPUID remains intercepted, but its answers come from the host CPU with hardware-randomness and unvirtualized timing features hidden. Results are host-CPU-model specific: cross-host builds need the same CPU model and compatible kernel/XSTATE settings and CPU topology. The tracer and guest are pinned to the lowest originally allowed CPU, even with the timeslice disabled; repeat runs require the same allowed CPU set. Host XSAVE behavior is retained without the x86-64-v3 XSTATE qualification, so programs inspecting XSAVE or signal-register metadata have no determinism guarantee. Programs must honor the advertised feature bits; unconditional RDRAND or RDSEED is not trapped by this profile.\n\nv3 is offered only on the ptrace backend, on hosts that pass a startup qualification (`hermit host-capabilities --cpu-profile x86-64-v3` runs it alone). A recording binds the host facts its guest\'s answers come from, and replay refuses a host where any of them differs (<https://github.com/rrnewton/hermit/issues/4243>).\n\nWith --cpu-profile x86-64-v3, Hermit checks at startup that this host does not change the XSTATE_BV bits a guest reads (with XSAVE, XSAVEC or XSAVEOPT, or in a signal frame) when the host saves and restores the guest\'s registers. The check samples a fixed set of cases and forces only CPUID exits, so a CPU or hypervisor that behaves differently only on other instruction paths, or on VM exits the guest cannot see, is not excluded. Firmware (SMM) entries cannot be checked at all. Default runs use x86-64-v2, which this does not affect.";

The long help of --cpu-profile, for hermit run and hermit record start.