From: vladimir.murzin@arm•com (Vladimir Murzin)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/6] make memtest a generic kernel feature
Date: Tue, 17 Mar 2015 17:20:31 +0000 [thread overview]
Message-ID: <5508625F.6060600@arm.com> (raw)
In-Reply-To: <20150317171822.GW8399@arm.com>
On 17/03/15 17:18, Will Deacon wrote:
> On Mon, Mar 09, 2015 at 10:27:04AM +0000, Vladimir Murzin wrote:
>> Memtest is a simple feature which fills the memory with a given set of
>> patterns and validates memory contents, if bad memory regions is detected it
>> reserves them via memblock API. Since memblock API is widely used by other
>> architectures this feature can be enabled outside of x86 world.
>>
>> This patch set promotes memtest to live under generic mm umbrella and enables
>> memtest feature for arm/arm64.
>>
>> It was reported that this patch set was useful for tracking down an issue with
>> some errant DMA on an arm64 platform.
>>
>> Since it touches x86 and mm bits it'd be great to get ACK/NAK for these bits.
>
> Is your intention for akpm to merge this? I don't mind how it goes upstream,
> but that seems like a sensible route to me.
>
It is already in -mm tree.
Vladimir
> Will
>
>> Changelog:
>>
>> RFC -> v1
>> - updated kernel-parameters.txt for memtest entry
>> - updated number of test patterns in Kconfig menu
>> - added Acked/Tested tags for arm64 bits
>> - rebased on v4.0-rc3
>>
>> Vladimir Murzin (6):
>> mm: move memtest under /mm
>> memtest: use phys_addr_t for physical addresses
>> arm64: add support for memtest
>> arm: add support for memtest
>> Kconfig: memtest: update number of test patterns up to 17
>> Documentation: update arch list in the 'memtest' entry
>>
>> Documentation/kernel-parameters.txt | 2 +-
>> arch/arm/mm/init.c | 3 +
>> arch/arm64/mm/init.c | 2 +
>> 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 +++++++++++++++++++++++++++++++++++
>> 11 files changed, 144 insertions(+), 140 deletions(-)
>> delete mode 100644 arch/x86/mm/memtest.c
>> create mode 100644 mm/memtest.c
>>
>> --
>> 1.7.9.5
>>
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo at kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack•org"> email at kvack.org </a>
>
>
>
next prev parent reply other threads:[~2015-03-17 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 10:27 [PATCH 0/6] make memtest a generic kernel feature Vladimir Murzin
2015-03-09 10:27 ` [PATCH 1/6] mm: move memtest under /mm Vladimir Murzin
2015-03-09 10:27 ` [PATCH 2/6] memtest: use phys_addr_t for physical addresses Vladimir Murzin
2015-03-09 10:27 ` [PATCH 3/6] arm64: add support for memtest Vladimir Murzin
2015-03-09 10:27 ` [PATCH 4/6] arm: " Vladimir Murzin
2015-03-09 10:27 ` [PATCH 5/6] Kconfig: memtest: update number of test patterns up to 17 Vladimir Murzin
2015-03-09 10:27 ` [PATCH 6/6] Documentation: update arch list in the 'memtest' entry Vladimir Murzin
2015-03-17 17:18 ` [PATCH 0/6] make memtest a generic kernel feature Will Deacon
2015-03-17 17:20 ` Vladimir Murzin [this message]
2015-03-17 17:31 ` Will Deacon
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=5508625F.6060600@arm.com \
--to=vladimir.murzin@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox