On 8/26/19 9:57 AM, Igor Mammedov wrote:
>
>> I most likely don't understand how this is supposed to work but aren't
>> we here successfully reading SMRAM from non-SMM context, something we
>> are not supposed to be able to do?
> We are aren't reading SMRAM at 0x3 base directly,
> "RAM" marked
On Fri, 16 Aug 2019 18:43:11 -0400
Boris Ostrovsky wrote:
> On 8/16/19 7:24 AM, Igor Mammedov wrote:
> > for purpose of demo SMRAM (at 0x3) is aliased at a in system
> > address space
> > for easy initialization of SMI entry point.
> > Here is resulting debug output showing that RAM at
On 8/16/19 7:24 AM, Igor Mammedov wrote:
> for purpose of demo SMRAM (at 0x3) is aliased at a in system address
> space
> for easy initialization of SMI entry point.
> Here is resulting debug output showing that RAM at 0x3 is not affected
> by SMM and only RAM in SMM adderss space is
for purpose of demo SMRAM (at 0x3) is aliased at a in system address
space
for easy initialization of SMI entry point.
Here is resulting debug output showing that RAM at 0x3 is not affected
by SMM and only RAM in SMM adderss space is modified:
init smm
smm_relocate: before relocaten
