Correct "MTTR" to "MTRR"
The term MTRR has been misspelled in a few places. Change-Id: I3e3c11f80de331fa45ae89779f2b8a74a0097c74 Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Reviewed-on: https://review.coreboot.org/25568 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
committed by
Patrick Georgi
parent
2e744e0fa5
commit
bb3a5efaf7
@ -1348,7 +1348,7 @@ SetupStack:
|
||||
mov $TOP_MEM2, %ecx # MSR:C001_001D
|
||||
_WRMSR
|
||||
|
||||
# setup MTTRs for stacks
|
||||
# setup MTRRs for stacks
|
||||
# A speculative read can be generated by a speculative fetch mis-aligned in a code zone
|
||||
# or due to a data zone being interpreted as code. When a speculative read occurs outside a
|
||||
# controlled region (intentionally used by software), it could cause an unwanted cache eviction.
|
||||
|
@ -1084,7 +1084,7 @@ SetupStack:
|
||||
mov $TOP_MEM2, %ecx # MSR:C001_001D
|
||||
_WRMSR
|
||||
|
||||
# setup MTTRs for stacks
|
||||
# setup MTRRs for stacks
|
||||
# A speculative read can be generated by a speculative fetch mis-aligned in a code zone
|
||||
# or due to a data zone being interpreted as code. When a speculative read occurs outside a
|
||||
# controlled region (intentionally used by software), it could cause an unwanted cache eviction.
|
||||
|
@ -1063,7 +1063,7 @@ SetupStack:
|
||||
mov $TOP_MEM2, %ecx # MSR:C001_001D
|
||||
_WRMSR
|
||||
|
||||
# setup MTTRs for stacks
|
||||
# setup MTRRs for stacks
|
||||
# A speculative read can be generated by a speculative fetch mis-aligned in a code zone
|
||||
# or due to a data zone being interpreted as code. When a speculative read occurs outside a
|
||||
# controlled region (intentionally used by software), it could cause an unwanted cache eviction.
|
||||
|
@ -1063,7 +1063,7 @@ SetupStack:
|
||||
mov $TOP_MEM2, %ecx # MSR:C001_001D
|
||||
_WRMSR
|
||||
|
||||
# setup MTTRs for stacks
|
||||
# setup MTRRs for stacks
|
||||
# A speculative read can be generated by a speculative fetch mis-aligned in a code zone
|
||||
# or due to a data zone being interpreted as code. When a speculative read occurs outside a
|
||||
# controlled region (intentionally used by software), it could cause an unwanted cache eviction.
|
||||
|
Reference in New Issue
Block a user