From: Randy Dunlap <rdunlap@infradead.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"arnd@arndb.de" <arnd@arndb.de>,
Mark Rutland <Mark.Rutland@arm.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: [RFC PATCH 1/4] mm: move memtest under /mm
Date: Tue, 03 Mar 2015 09:46:41 -0800 [thread overview]
Message-ID: <54F5F381.30104@infradead.org> (raw)
In-Reply-To: <54F57D4C.9010909@arm.com>
On 03/03/15 01:22, Vladimir Murzin wrote:
> On 03/03/15 01:52, Randy Dunlap wrote:
>> 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@arm.com>
>>> ---
>>> 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?
>>
>
> Yes, that correct. Additional patterns were introduced since 63823126
> "x86: memtest: add additional (regular) test patterns", but looks like
> Kconfig was not updated that time. Do you want me to fold updates for
> that info or make a separate patch?
Either is OK with me but it probably should be a separate patch.
Thanks.
--
~Randy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"arnd@arndb.de" <arnd@arndb.de>,
Mark Rutland <Mark.Rutland@arm.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: [RFC PATCH 1/4] mm: move memtest under /mm
Date: Tue, 03 Mar 2015 09:46:41 -0800 [thread overview]
Message-ID: <54F5F381.30104@infradead.org> (raw)
Message-ID: <20150303174641.V2KsdehpDjEZK0kWdBZhbNEks-YuLVvy4f-kZxLc_zA@z> (raw)
In-Reply-To: <54F57D4C.9010909@arm.com>
On 03/03/15 01:22, Vladimir Murzin wrote:
> On 03/03/15 01:52, Randy Dunlap wrote:
>> 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@arm.com>
>>> ---
>>> 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?
>>
>
> Yes, that correct. Additional patterns were introduced since 63823126
> "x86: memtest: add additional (regular) test patterns", but looks like
> Kconfig was not updated that time. Do you want me to fold updates for
> that info or make a separate patch?
Either is OK with me but it probably should be a separate patch.
Thanks.
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: rdunlap@infradead.org (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/4] mm: move memtest under /mm
Date: Tue, 03 Mar 2015 09:46:41 -0800 [thread overview]
Message-ID: <54F5F381.30104@infradead.org> (raw)
In-Reply-To: <54F57D4C.9010909@arm.com>
On 03/03/15 01:22, Vladimir Murzin wrote:
> On 03/03/15 01:52, Randy Dunlap wrote:
>> 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@arm.com>
>>> ---
>>> 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?
>>
>
> Yes, that correct. Additional patterns were introduced since 63823126
> "x86: memtest: add additional (regular) test patterns", but looks like
> Kconfig was not updated that time. Do you want me to fold updates for
> that info or make a separate patch?
Either is OK with me but it probably should be a separate patch.
Thanks.
--
~Randy
next prev parent reply other threads:[~2015-03-03 17:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 14:55 [RFC PATCH 0/4] make memtest a generic kernel feature Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` [RFC PATCH 1/4] mm: move memtest under /mm Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-03 1:52 ` Randy Dunlap
2015-03-03 1:52 ` Randy Dunlap
2015-03-03 1:52 ` Randy Dunlap
2015-03-03 9:22 ` Vladimir Murzin
2015-03-03 9:22 ` Vladimir Murzin
2015-03-03 9:22 ` Vladimir Murzin
2015-03-03 17:46 ` Randy Dunlap [this message]
2015-03-03 17:46 ` Randy Dunlap
2015-03-03 17:46 ` Randy Dunlap
2015-03-02 14:55 ` [RFC PATCH 2/4] memtest: use phys_addr_t for physical addresses Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` [RFC PATCH 3/4] arm64: add support for memtest Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 18:56 ` Will Deacon
2015-03-02 18:56 ` Will Deacon
2015-03-02 18:56 ` Will Deacon
2015-03-03 9:26 ` Vladimir Murzin
2015-03-03 9:26 ` Vladimir Murzin
2015-03-03 9:26 ` Vladimir Murzin
2015-03-03 14:14 ` Catalin Marinas
2015-03-03 14:14 ` Catalin Marinas
2015-03-03 14:14 ` Catalin Marinas
2015-03-02 14:55 ` [RFC PATCH 4/4] arm: " Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 15:14 ` [RFC PATCH 0/4] make memtest a generic kernel feature Baruch Siach
2015-03-02 15:14 ` Baruch Siach
2015-03-02 15:14 ` Baruch Siach
2015-03-03 9:28 ` Vladimir Murzin
2015-03-03 9:28 ` Vladimir Murzin
2015-03-03 9:28 ` Vladimir Murzin
2015-03-03 16:37 ` Mark Rutland
2015-03-03 16:37 ` Mark Rutland
2015-03-03 16:37 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F5F381.30104@infradead.org \
--to=rdunlap@infradead.org \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Will.Deacon@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=lauraa@codeaurora.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vladimir.murzin@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.