Lines Matching defs:fields
116 * processor cannot vmwrite to fields that don't exist
1548 * Copy the writable VMCS shadow fields back to the VMCS12, in case they have
1551 * fields tagged SHADOW_FIELD_RO may or may not align with the "read-only"
1552 * VM-exit information fields (which are actually writable if the vCPU is
1584 const struct shadow_vmcs_field *fields[] = {
1603 for (q = 0; q < ARRAY_SIZE(fields); q++) {
1605 field = fields[q][i];
1809 * Read only fields:
2059 * reloaded from guest's memory (read only fields, fields not
2072 * Clean fields data can't be used on VMLAUNCH and when we switch
2088 /* All fields are clean */
2167 * fields that come from L0 and are not constant, e.g. HOST_CR3,
2301 /* Take the following fields only from vmcs12 */
2523 * vcpu->arch fields.
2800 * These fields are the VM-entry interruption-information field, the
4087 * Update the guest state fields of vmcs12 to reflect changes that
4165 * Note that we do not have to copy here all VMCS fields, just those that
4167 * exit-information fields only. Other fields are modified by L1 with VMWRITE,
4174 /* update exit information fields: */
4181 * exit info fields are unmodified.
4509 * now and the new vmentry. Ensure that the VMCS02 PDPTR fields are
4576 /* Update any VMCS fields that might have changed while L2 ran */
5012 /* copy to memory all shadowed fields in case
5239 * VMCS," then the "read-only" fields are actually read/write.
5254 * fields on VMWRITE. Emulate this behavior to ensure consistent KVM
5273 * L1 can read these fields without exiting, ensure the
5830 /* Out-of-range fields always cause a VM exit from L2 to L1 */
6417 * The same values should also be used to verify that vmcs12 control fields are
6428 * the control fields which may be 1) should be initialized by the
6436 * fields of vmcs01 and vmcs02, will turn these bits off - and