Re: [PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state

2025-06-16 Thread Ani Sinha
> On 12 Jun 2025, at 5:33 PM, Ani Sinha wrote: > > > >> On 27 Feb 2025, at 7:59 PM, 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 i

Re: [PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state

2025-06-12 Thread Ani Sinha
> On 27 Feb 2025, at 7:59 PM, 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 populate vm

Re: [PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state

2025-02-27 Thread Gupta, Pankaj
On 2/27/2025 3:29 PM, 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 populate vmcb_save_area for each C

[PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state

2025-02-27 Thread Roy Hopkins
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 start