From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Baruch Siach <baruch@tkos.co.il>
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>,
Mark Rutland <Mark.Rutland@arm.com>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 0/4] make memtest a generic kernel feature
Date: Tue, 03 Mar 2015 09:28:39 +0000 [thread overview]
Message-ID: <54F57EC7.1060202@arm.com> (raw)
In-Reply-To: <20150302151400.GI15668@tarshish>
On 02/03/15 15:14, Baruch Siach wrote:
> Hi Vladimir,
>
> On Mon, Mar 02, 2015 at 02:55:41PM +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.
>
> Please update the architectures list in the 'memtest' entry at
> Documentation/kernel-parameters.txt.
Thanks for pointing at it. I'll add updates for documentation to my next
version.
Vladimir
>
> baruch
>
next prev parent reply other threads:[~2015-03-03 9:28 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 [this message]
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=54F57EC7.1060202@arm.com \
--to=vladimir.murzin@arm.com \
--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=baruch@tkos.co.il \
--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).