> From: Tamas K Lengyel <ta...@tklengyel.com> > Sent: Tuesday, April 19, 2022 2:43 AM > > On Fri, Mar 25, 2022 at 9:34 AM Tamas K Lengyel <tamas.leng...@intel.com> > wrote: > > > > During VM forking and resetting a failed vmentry has been observed due > > to the guest non-register state going out-of-sync with the guest register > > state. For example, a VM fork reset right after a STI instruction can > > trigger > > the failed entry. This is due to the guest non-register state not being > > saved > > from the parent VM, thus the reset operation only copies the register state. > > > > Fix this by adding a new pair of hvm functions to get/set the guest > > non-register state so that the overall vCPU state remains in sync. > > > > Signed-off-by: Tamas K Lengyel <tamas.leng...@intel.com> > > --- > > v5: Switch to internal-only hvm funcs instead of adding to hvm_hw_cpu > > Patch ping.
I'd like to hear opinions from Andrew/Jan first. Obviously they have different thoughts when reviewing the earlier versions.
