On 03/02/15 06:55, Vladimir Murzin wrote: > There is nothing platform dependent in the core memtest code, so other platform > might benefit of this feature too. > > Signed-off-by: Vladimir Murzin <vladimir.murzin@xxxxxxx> > --- > arch/x86/Kconfig | 11 ---- > arch/x86/include/asm/e820.h | 8 --- > arch/x86/mm/Makefile | 2 - > arch/x86/mm/memtest.c | 118 ------------------------------------------- > include/linux/memblock.h | 8 +++ > lib/Kconfig.debug | 11 ++++ > mm/Makefile | 1 + > mm/memtest.c | 118 +++++++++++++++++++++++++++++++++++++++++++ > 8 files changed, 138 insertions(+), 139 deletions(-) > delete mode 100644 arch/x86/mm/memtest.c > create mode 100644 mm/memtest.c > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index c5cefb3..8eb064fd 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1732,6 +1732,17 @@ config TEST_UDELAY > > If unsure, say N. > > +config MEMTEST > + bool "Memtest" > + ---help--- > + This option adds a kernel parameter 'memtest', which allows memtest > + to be set. > + memtest=0, mean disabled; -- default > + memtest=1, mean do 1 test pattern; > + ... > + memtest=4, mean do 4 test patterns. This sort of implies a max of 4 test patterns, but it seems to be 17 if I counted correctly, so if someone wants to test all of the possible 'memtest' patterns, they would need to use 'memtest=17', is that correct? > + If you are unsure how to answer this question, answer N. Thanks, -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
