cpu/x86/smm/smihandler.c: Simplify smm revision handling
The ASEG smihandler bails out if an unsupported SMM save state revision is detected. Now we have code to find the SMM save state depending on the SMM save state revision so reuse this to do the same. This also increases the loglevel when bailing out of SMM due to unsupported SMM save state revision from BIOS_DEBUG to BIOS_WARNING, given that the system likely still boots but won't have a functioning smihandler. Change-Id: I57198f0c85c0f7a1fa363d3bd236c3d41b68d2f0 Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://review.coreboot.org/c/coreboot/+/45471 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
This commit is contained in:
parent
4067fa3512
commit
a69d2c10a9
|
@ -14,23 +14,6 @@
|
||||||
#include <spi-generic.h>
|
#include <spi-generic.h>
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
typedef enum {
|
|
||||||
AMD64,
|
|
||||||
EM64T100,
|
|
||||||
EM64T101,
|
|
||||||
LEGACY
|
|
||||||
} save_state_type_t;
|
|
||||||
|
|
||||||
typedef struct {
|
|
||||||
save_state_type_t type;
|
|
||||||
union {
|
|
||||||
amd64_smm_state_save_area_t *amd64_state_save;
|
|
||||||
em64t100_smm_state_save_area_t *em64t100_state_save;
|
|
||||||
em64t101_smm_state_save_area_t *em64t101_state_save;
|
|
||||||
legacy_smm_state_save_area_t *legacy_state_save;
|
|
||||||
};
|
|
||||||
} smm_state_save_area_t;
|
|
||||||
|
|
||||||
static int do_driver_init = 1;
|
static int do_driver_init = 1;
|
||||||
|
|
||||||
typedef enum { SMI_LOCKED, SMI_UNLOCKED } smi_semaphore;
|
typedef enum { SMI_LOCKED, SMI_UNLOCKED } smi_semaphore;
|
||||||
|
@ -162,9 +145,6 @@ bool smm_region_overlaps_handler(const struct region *r)
|
||||||
void smi_handler(void)
|
void smi_handler(void)
|
||||||
{
|
{
|
||||||
unsigned int node;
|
unsigned int node;
|
||||||
const uint32_t smm_rev = smm_revision();
|
|
||||||
smm_state_save_area_t state_save;
|
|
||||||
u32 smm_base = SMM_BASE; /* ASEG */
|
|
||||||
|
|
||||||
/* Are we ok to execute the handler? */
|
/* Are we ok to execute the handler? */
|
||||||
if (!smi_obtain_lock()) {
|
if (!smi_obtain_lock()) {
|
||||||
|
@ -190,36 +170,10 @@ void smi_handler(void)
|
||||||
|
|
||||||
printk(BIOS_SPEW, "\nSMI# #%d\n", node);
|
printk(BIOS_SPEW, "\nSMI# #%d\n", node);
|
||||||
|
|
||||||
switch (smm_rev) {
|
/* Use smm_get_save_state() to see if the smm revision is supported */
|
||||||
case 0x00030002:
|
if (smm_get_save_state(node) == NULL) {
|
||||||
case 0x00030007:
|
printk(BIOS_WARNING, "smm_revision: 0x%08x\n", smm_revision());
|
||||||
state_save.type = LEGACY;
|
printk(BIOS_WARNING, "SMI# not supported on your CPU\n");
|
||||||
state_save.legacy_state_save =
|
|
||||||
smm_save_state(smm_base,
|
|
||||||
SMM_LEGACY_ARCH_OFFSET, node);
|
|
||||||
break;
|
|
||||||
case 0x00030100:
|
|
||||||
state_save.type = EM64T100;
|
|
||||||
state_save.em64t100_state_save =
|
|
||||||
smm_save_state(smm_base,
|
|
||||||
SMM_EM64T100_ARCH_OFFSET, node);
|
|
||||||
break;
|
|
||||||
case 0x00030101: /* SandyBridge, IvyBridge, and Haswell */
|
|
||||||
state_save.type = EM64T101;
|
|
||||||
state_save.em64t101_state_save =
|
|
||||||
smm_save_state(smm_base,
|
|
||||||
SMM_EM64T101_ARCH_OFFSET, node);
|
|
||||||
break;
|
|
||||||
case 0x00020064:
|
|
||||||
case 0x00030064:
|
|
||||||
state_save.type = AMD64;
|
|
||||||
state_save.amd64_state_save =
|
|
||||||
smm_save_state(smm_base,
|
|
||||||
SMM_AMD64_ARCH_OFFSET, node);
|
|
||||||
break;
|
|
||||||
default:
|
|
||||||
printk(BIOS_DEBUG, "smm_revision: 0x%08x\n", smm_rev);
|
|
||||||
printk(BIOS_DEBUG, "SMI# not supported on your CPU\n");
|
|
||||||
/* Don't release lock, so no further SMI will happen,
|
/* Don't release lock, so no further SMI will happen,
|
||||||
* if we don't handle it anyways.
|
* if we don't handle it anyways.
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Reference in New Issue