summaryrefslogtreecommitdiff
path: root/src/mainboard/google/glados/gpio.h
diff options
context:
space:
mode:
authorTimothy Pearson <tpearson@raptorengineeringinc.com>2015-08-12 11:19:10 -0500
committerAlexandru Gagniuc <mr.nuke.me@gmail.com>2015-08-14 01:16:22 +0200
commit27baa32fbefa19afe2bc96b60f534ca20cb49065 (patch)
tree2c6d9b53cd42c08bdcf3c58ff46ae5fa21770078 /src/mainboard/google/glados/gpio.h
parente3260ec29a0bce2d57ba66b99ea1d87a56e1e18a (diff)
downloadcoreboot-27baa32fbefa19afe2bc96b60f534ca20cb49065.tar.xz
cpu/amd/model_10xxx: Do not initialize SMM memory if SMM is disabled
In the wake of the recent Intel "Memoy Sinkhole" exploit a code review of the AMD SMM code was undertaken. While native Family 10h support does not appear to be affected by the same SMM flaw, it also does not require SMM to function. Therefore, the SMM memory range initialization should only be executed if SMM will be used on the target platform. Change-Id: I6531908a7724933e4ba5a2bbefeb89356197e8fd Signed-off-by: Timothy Pearson <tpearson@raptorengineeringinc.com> Reviewed-on: http://review.coreboot.org/11211 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'src/mainboard/google/glados/gpio.h')
0 files changed, 0 insertions, 0 deletions