[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Mar 2015 14:14:49 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Vladimir Murzin <vladimir.murzin@....com>
Cc: Will Deacon <will.deacon@....com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
Mark Rutland <Mark.Rutland@....com>,
"lauraa@...eaurora.org" <lauraa@...eaurora.org>,
"arnd@...db.de" <arnd@...db.de>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH 3/4] arm64: add support for memtest
On Tue, Mar 03, 2015 at 09:26:58AM +0000, Vladimir Murzin wrote:
> On 02/03/15 18:56, Will Deacon wrote:
> > On Mon, Mar 02, 2015 at 02:55:44PM +0000, Vladimir Murzin wrote:
> >> Add support for memtest command line option.
> >>
> >> Signed-off-by: Vladimir Murzin <vladimir.murzin@....com>
> >> ---
> >> arch/arm64/mm/init.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> >> index ae85da6..597831b 100644
> >> --- a/arch/arm64/mm/init.c
> >> +++ b/arch/arm64/mm/init.c
> >> @@ -190,6 +190,8 @@ void __init bootmem_init(void)
> >> min = PFN_UP(memblock_start_of_DRAM());
> >> max = PFN_DOWN(memblock_end_of_DRAM());
> >>
> >> + early_memtest(min << PAGE_SHIFT, max << PAGE_SHIFT);
> >> +
> >> /*
> >> * Sparsemem tries to allocate bootmem in memory_present(), so must be
> >> * done after the fixed reservations.
> >
> > This is really neat, thanks for doing this Vladimir!
> >
> > Acked-by: Will Deacon <will.deacon@....com>
> >
> > For the series, modulo Baruch's comments about Documentation updates.
>
> Thanks Will! I'll wait for awhile for other comments and repost updated
> version.
>
> I wonder which tree it might go?
Since it touches mm, x86, arm, arm64, I guess it could go in via the mm
tree (akpm). We could take it via the arm64 tree as well if we have all
the acks in place.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists