summaryrefslogtreecommitdiffstats
diff options
authordavejiang <dokuwiki@localhost>2018-08-10 16:17:03 +0000
committerKonstantin Ryabitsev <konstantin@linuxfoundation.org>2024-09-26 14:36:54 -0400
commitcb3ec0ca05b6d5c9a5700475dd7dedb1ac9701f2 (patch)
tree2f487d8e843bc15bb40aff51f6e57d50c6bb3e87
parent502f6441e8e6e67cc5abf5f1400bdfd0df240e5c (diff)
downloadnvdimm-cb3ec0ca05b6d5c9a5700475dd7dedb1ac9701f2.tar.gz
how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system:
-rw-r--r--source/how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/source/how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system.txt b/source/how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system.txt
index 286c16c..992253a 100644
--- a/source/how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system.txt
+++ b/source/how_to_choose_the_correct_memmap_kernel_parameter_for_pmem_on_your_system.txt
@@ -127,3 +127,8 @@ The "System RAM" region now sits in the middle of my "Persistent Memory (legacy)
[ 6.357757] devm_memremap_pages attempted on mixed region [mem 0x4e968c000-0x4ffffffff flags 0x200]
</code>
and no /dev/pmem* devices being created.
+
+The CONFIG_RANDOMIZE_BASE (KASLR) issue should have been fixed:
+f28442497b5caf ("x86/boot: Fix KASLR and memmap= collision")
+
+There seems to be an issue with CONFIG_KSAN at the moment however.