Lines Matching full:policy
42 the firmware. To create this context, guest owner must provide a guest policy,
46 The guest policy is passed as plaintext. A hypervisor may choose to read it,
47 but should not modify it (any modification of the policy bits will result
48 in bad measurement). The guest policy is a 4-byte data structure containing
52 The guest policy can be provided via the ``policy`` property::
55 sev-guest,id=sev0,policy=0x1...\
57 Setting the "SEV-ES required" policy bit (bit 2) will launch the guest as a
61 sev-guest,id=sev0,policy=0x5...\
108 -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x5
133 HMAC(0x04 || API_MAJOR || API_MINOR || BUILD || GCTX.POLICY || GCTX.LD || MNONCE; GCTX.TIK)
137 The values of API_MAJOR, API_MINOR, BUILD, and GCTX.POLICY can be obtained
156 * if SEV-ES is enabled (``policy & 0x4 != 0``), ``vmsas_blob`` is the
176 guest policy and other parameters as described in the SEV-SNP firmware
187 | policy | hex | 0x30000 | a 64-bit guest policy |
234 the guest memory will return cipher text. If the guest policy allows debugging,