Re: [edk2] [PATCH v4 13/41] OvmfPkg: LockBox: -D SMM_REQUIRE excludes our fake lockbox

On 11/11/15 22:25, Jordan Justen wrote: > On 2015-11-03 13:00:49, Laszlo Ersek wrote: >> When the user builds OVMF with -D SMM_REQUIRE, our LockBox implementation >> must not be used, since it doesn't actually protect data in the LockBox >> from the runtime guest OS. Add an according assert to >> L

Re: [edk2] [PATCH v4 13/41] OvmfPkg: LockBox: -D SMM_REQUIRE excludes our fake lockbox

On 2015-11-03 13:00:49, Laszlo Ersek wrote: > When the user builds OVMF with -D SMM_REQUIRE, our LockBox implementation > must not be used, since it doesn't actually protect data in the LockBox > from the runtime guest OS. Add an according assert to > LockBoxLibInitialize(). > > Furthermore, since

Re: [edk2] [PATCH v4 13/41] OvmfPkg: LockBox: -D SMM_REQUIRE excludes our fake lockbox

On 11/04/15 09:52, Paolo Bonzini wrote: > > > On 03/11/2015 22:00, Laszlo Ersek wrote: >> When the user builds OVMF with -D SMM_REQUIRE, our LockBox implementation >> must not be used, since it doesn't actually protect data in the LockBox >> from the runtime guest OS. Add an according assert to >

Re: [edk2] [PATCH v4 13/41] OvmfPkg: LockBox: -D SMM_REQUIRE excludes our fake lockbox

On 03/11/2015 22:00, Laszlo Ersek wrote: > When the user builds OVMF with -D SMM_REQUIRE, our LockBox implementation > must not be used, since it doesn't actually protect data in the LockBox > from the runtime guest OS. Add an according assert to > LockBoxLibInitialize(). > > Furthermore, since

[edk2] [PATCH v4 13/41] OvmfPkg: LockBox: -D SMM_REQUIRE excludes our fake lockbox

When the user builds OVMF with -D SMM_REQUIRE, our LockBox implementation must not be used, since it doesn't actually protect data in the LockBox from the runtime guest OS. Add an according assert to LockBoxLibInitialize(). Furthermore, since our LockBox must not be selected with -D SMM_REQUIRE, i