diff options
| author |   Ying-Tsun Huang <ying-tsun.huang@amd.com> | 2020-12-15 15:07:20 +0800 |
|---|---|---|
| committer |   Borislav Petkov <bp@suse.de> | 2021-01-06 13:01:13 +0100 |
| commit | cb7f4a8b1fb426a175d1708f05581939c61329d4 (patch) | |
| tree | cb0db9cc1c688b9341e40cdaabc744750ab145d4 /arch/x86/kernel/cpu/resctrl/rdtgroup.c | |
| parent | x86/sev-es: Fix SEV-ES OUT/IN immediate opcode vc handling (diff) | |
| download | linux-dev-cb7f4a8b1fb426a175d1708f05581939c61329d4.tar.xz linux-dev-cb7f4a8b1fb426a175d1708f05581939c61329d4.zip | |
x86/mtrr: Correct the range check before performing MTRR type lookups
In mtrr_type_lookup(), if the input memory address region is not in the
MTRR, over 4GB, and not over the top of memory, a write-back attribute
is returned. These condition checks are for ensuring the input memory
address region is actually mapped to the physical memory.
However, if the end address is just aligned with the top of memory,
the condition check treats the address is over the top of memory, and
write-back attribute is not returned.
And this hits in a real use case with NVDIMM: the nd_pmem module tries
to map NVDIMMs as cacheable memories when NVDIMMs are connected. If a
NVDIMM is the last of the DIMMs, the performance of this NVDIMM becomes
very low since it is aligned with the top of memory and its memory type
is uncached-minus.
Move the input end address change to inclusive up into
mtrr_type_lookup(), before checking for the top of memory in either
mtrr_type_lookup_{variable,fixed}() helpers.
[ bp: Massage commit message. ]
Fixes: 0cc705f56e40 ("x86/mm/mtrr: Clean up mtrr_type_lookup()")
Signed-off-by: Ying-Tsun Huang <ying-tsun.huang@amd.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/20201215070721.4349-1-ying-tsun.huang@amd.com
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions