From: Mark Rutland <mark.rutland@arm.com>
To: Vladimir Murzin <Vladimir.Murzin@arm.com>
Cc: "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>,
"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>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: [RFC PATCH 0/4] make memtest a generic kernel feature
Date: Tue, 3 Mar 2015 16:37:40 +0000 [thread overview]
Message-ID: <20150303163740.GA10239@leverpostej> (raw)
In-Reply-To: <1425308145-20769-1-git-send-email-vladimir.murzin@arm.com>
On Mon, Mar 02, 2015 at 02:55:41PM +0000, Vladimir Murzin wrote:
> Hi,
Hi Vladimir,
> 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.
>
> Patches are built on top of 4.0-rc1
Thanks for putting this together. I've found this extremely useful for
tracking down an issue with some errant DMA on an arm64 platform. For
the first three patches:
Tested-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
>
> Vladimir Murzin (4):
> mm: move memtest under /mm
> memtest: use phys_addr_t for physical addresses
> arm64: add support for memtest
> arm: add support for memtest
>
> 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 +++++++++++++++++++++++++++++++++++++++++++
> 10 files changed, 143 insertions(+), 139 deletions(-)
> delete mode 100644 arch/x86/mm/memtest.c
> create mode 100644 mm/memtest.c
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2015-03-03 16:37 UTC|newest]
Thread overview: 21+ 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 ` [RFC PATCH 1/4] mm: move memtest under /mm Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-03 1:52 ` Randy Dunlap
2015-03-03 9:22 ` Vladimir Murzin
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 ` [RFC PATCH 3/4] arm64: add support for memtest Vladimir Murzin
2015-03-02 14:55 ` Vladimir Murzin
2015-03-02 18:56 ` Will Deacon
2015-03-03 9:26 ` Vladimir Murzin
2015-03-03 9:26 ` Vladimir Murzin
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 15:14 ` [RFC PATCH 0/4] make memtest a generic kernel feature Baruch Siach
2015-03-03 9:28 ` Vladimir Murzin
2015-03-03 16:37 ` Mark Rutland [this message]
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=20150303163740.GA10239@leverpostej \
--to=mark.rutland@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Vladimir.Murzin@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).