>
> btw it still fails in CoreTerminateMemoryMap() with the current upstream
> kernel which is not aware of the lazy memory acceptance, is this
> something known? Thanks,
>
It wasn't known. I'll take a look. Thanks for the report.
--
-Dionna Glaze, PhD (she/her)
-=-=-=-=-=-=-=-=-=-=-=-
Groups.
On 26/10/2022 13:49, Alexey Kardashevskiy wrote:
On 26/10/2022 12:35, Alexey Kardashevskiy wrote:
On 26/10/2022 12:07, Dionna Amalie Glaze wrote:
On Tue, Oct 25, 2022 at 5:23 PM Alexey Kardashevskiy
wrote:
Hi Dionna,
Thanks for updating the tree, builds nicely now! However the VM's
On 26/10/2022 12:35, Alexey Kardashevskiy wrote:
On 26/10/2022 12:07, Dionna Amalie Glaze wrote:
On Tue, Oct 25, 2022 at 5:23 PM Alexey Kardashevskiy
wrote:
Hi Dionna,
Thanks for updating the tree, builds nicely now! However the VM's kernel
does not boot - the guest kernel reports
EFI
On 26/10/2022 12:07, Dionna Amalie Glaze wrote:
On Tue, Oct 25, 2022 at 5:23 PM Alexey Kardashevskiy wrote:
Hi Dionna,
Thanks for updating the tree, builds nicely now! However the VM's kernel
does not boot - the guest kernel reports
EFI stub: ERROR: exit_boot() failed!
and hangs. I am no
On Tue, Oct 25, 2022 at 5:23 PM Alexey Kardashevskiy wrote:
>
> Hi Dionna,
>
> Thanks for updating the tree, builds nicely now! However the VM's kernel
> does not boot - the guest kernel reports
>
> EFI stub: ERROR: exit_boot() failed!
>
> and hangs. I am not quite sure how it is supposed to work
Hi Dionna,
Thanks for updating the tree, builds nicely now! However the VM's kernel
does not boot - the guest kernel reports
EFI stub: ERROR: exit_boot() failed!
and hangs. I am not quite sure how it is supposed to work (still
learning) but "Accepting all memory" happens twice (should it?) a
Hey!
Sorry if this was asked. I was wondering if this patchset is in some git repo
which I pull from as I struggle to get a buildable tree by applying this
patchset to whatever I can find.
I tried https://github.com/deeglaze/edk2.git (
https://github.com/deeglaze/edk2.git ) enable_umv7 but it
>
> Hey!
>
> Sorry if this was asked. I was wondering if this patchset is in some git repo
> which I pull from as I struggle to get a buildable tree by applying this
> patchset to whatever I can find.
>
> I tried https://github.com/deeglaze/edk2.git enable_umv7 but it does not
> build (missing
> > I suppose that's true. Would you prefer volatile versions of
> > OsIndications/OsIndicationsSupported added to the spec, or this
> > proposed one-off toggle protocol? No specified global variables seem
> > overloadable with this duty.
> >
>
> No it would have to be a completely separate variabl
On Fri, 21 Oct 2022 at 00:37, Dionna Amalie Glaze
wrote:
>
> > That assumes the variable is non-volatile, but I suppose we could use
> > a volatile variable [other than OsIndications] as well.
> >
>
> I suppose that's true. Would you prefer volatile versions of
> OsIndications/OsIndicationsSupport
> That assumes the variable is non-volatile, but I suppose we could use
> a volatile variable [other than OsIndications] as well.
>
I suppose that's true. Would you prefer volatile versions of
OsIndications/OsIndicationsSupported added to the spec, or this
proposed one-off toggle protocol? No spec
On Fri, 14 Oct 2022 at 23:30, Dionna Glaze via groups.io
wrote:
>
> >
> > Can OsIndicationsSupported UEFI variable provide the similar functionality?
> >
>
> Similar, but not the same. If we use a UEFI variable, its value will
> persist across boots.
That assumes the variable is non-volatile, but
>
> Can OsIndicationsSupported UEFI variable provide the similar functionality?
>
Similar, but not the same. If we use a UEFI variable, its value will
persist across boots. This can be fine if you only boot one OS, but if
you have two where one supports unaccepted memory and the other
doesn't then
>
> To allow the OS loader to prevent the eager acceptance, we add a new
> protocol, up for standardization, AcceptAllUnacceptedMemoryProtocol.
> This protocol has one interface, Disable(). The OS loader can inform the
> UEFI that it supports the unaccepted memory type and accepts the
> responsibi
These seven patches build on the lazy-accept patch series
"Introduce Lazy-accept for Tdx guest"
by adding SEV-SNP support for the MemoryAccept protocol, and
importantly making eager memory acceptance the default behavior.
We implement a standardized event group from UEFI v2.9,
EFI_EVENT_GROUP_BE
15 matches
Mail list logo
