On Tue, 2024-03-12 at 16:12 +, Daniel P. Berrangé wrote:
> On Tue, Mar 12, 2024 at 03:45:20PM +, Roy Hopkins wrote:
> > On Fri, 2024-03-01 at 17:01 +, Daniel P. Berrangé wrote:
> > > On Tue, Feb 27, 2024 at 02:50:13PM +, Roy Hopkins wrote:
> > > > + /*
> > > > +
On Tue, Mar 12, 2024 at 03:45:20PM +, Roy Hopkins wrote:
> On Fri, 2024-03-01 at 17:01 +, Daniel P. Berrangé wrote:
> > On Tue, Feb 27, 2024 at 02:50:13PM +, Roy Hopkins wrote:
> > > + /*
> > > + * Ideally we would provide the VMSA directly to kvm which
> > >
On Fri, 2024-03-01 at 17:01 +, Daniel P. Berrangé wrote:
> On Tue, Feb 27, 2024 at 02:50:13PM +, Roy Hopkins wrote:
> > When an SEV guest is started, the reset vector and state are
> > extracted from metadata that is contained in the firmware volume.
> >
> > In preparation for using IGVM
On Tue, Feb 27, 2024 at 02:50:13PM +, Roy Hopkins wrote:
> When an SEV guest is started, the reset vector and state are
> extracted from metadata that is contained in the firmware volume.
>
> In preparation for using IGVM to setup the initial CPU state,
> the code has been refactored to
When an SEV guest is started, the reset vector and state are
extracted from metadata that is contained in the firmware volume.
In preparation for using IGVM to setup the initial CPU state,
the code has been refactored to populate vmcb_save_area for each
CPU which is then applied during guest
