SMM: don't overwrite SMM memory on resume
Overwriting the SMM Area on resume leaves us with all variables cleared out, i.e., the GNVS pointer is no longer available, which makes SMIF function calls impossible. Change-Id: I08ab4ffd41df0922d63c017822de1f89a3ff254d Signed-off-by: Sven Schnelle <svens@stackframe.org> Reviewed-on: http://review.coreboot.org/34 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
This commit is contained in:
@@ -320,6 +320,16 @@ static void smm_relocate(void)
|
||||
|
||||
static int smm_handler_copied = 0;
|
||||
|
||||
static int is_wakeup(void)
|
||||
{
|
||||
device_t dev0 = dev_find_slot(0, PCI_DEVFN(0,0));
|
||||
|
||||
if (!dev0)
|
||||
return 0;
|
||||
|
||||
return pci_read_config32(dev0, 0xdc) == SKPAD_ACPI_S3_MAGIC;
|
||||
}
|
||||
|
||||
static void smm_install(void)
|
||||
{
|
||||
/* The first CPU running this gets to copy the SMM handler. But not all
|
||||
@@ -329,13 +339,19 @@ static void smm_install(void)
|
||||
return;
|
||||
smm_handler_copied = 1;
|
||||
|
||||
/* enable the SMM memory window */
|
||||
pci_write_config8(dev_find_slot(0, PCI_DEVFN(0, 0)), SMRAM,
|
||||
D_OPEN | G_SMRAME | C_BASE_SEG);
|
||||
|
||||
/* copy the real SMM handler */
|
||||
memcpy((void *)0xa0000, &_binary_smm_start, (size_t)&_binary_smm_size);
|
||||
wbinvd();
|
||||
/* if we're resuming from S3, the SMM code is already in place,
|
||||
* so don't copy it again to keep the current SMM state */
|
||||
|
||||
if (!is_wakeup()) {
|
||||
/* enable the SMM memory window */
|
||||
pci_write_config8(dev_find_slot(0, PCI_DEVFN(0, 0)), SMRAM,
|
||||
D_OPEN | G_SMRAME | C_BASE_SEG);
|
||||
|
||||
/* copy the real SMM handler */
|
||||
memcpy((void *)0xa0000, &_binary_smm_start, (size_t)&_binary_smm_size);
|
||||
wbinvd();
|
||||
}
|
||||
|
||||
/* close the SMM memory window and enable normal SMM */
|
||||
pci_write_config8(dev_find_slot(0, PCI_DEVFN(0, 0)), SMRAM,
|
||||
|
Reference in New Issue
Block a user