[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d457aabc-9f58-f47e-f5fa-9539618b2759@huawei.com>
Date: Wed, 12 Aug 2020 09:07:44 +0800
From: Zefan Li <lizefan@...wei.com>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Nicholas Piggin <npiggin@...il.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
<linux-arch@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org>,
"Catalin Marinas" <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
<x86@...nel.org>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v3 0/8] huge vmalloc mappings
On 2020/8/12 0:32, Jonathan Cameron wrote:
> On Mon, 10 Aug 2020 12:27:24 +1000
> Nicholas Piggin <npiggin@...il.com> wrote:
>
>> Not tested on x86 or arm64, would appreciate a quick test there so I can
>> ask Andrew to put it in -mm. Other option is I can disable huge vmallocs
>> for them for the time being.
>
> Hi Nicholas,
>
> For arm64 testing with a Kunpeng920.
>
> I ran a quick sanity test with this series on top of mainline (yes mid merge window
> so who knows what state is...). Could I be missing some dependency?
>
> Without them it boots, with them it doesn't. Any immediate guesses?
>
I've already reported this bug in v2, and yeah I also tested it on arm64
(not Kunpeng though), so looks like it still hasn't been fixed.
...
>>
>> Since v2:
>> - Rebased on vmalloc cleanups, split series into simpler pieces.
>> - Fixed several compile errors and warnings
>> - Keep the page array and accounting in small page units because
>> struct vm_struct is an interface (this should fix x86 vmap stack debug
>> assert). [Thanks Zefan]
though the changelog says it's fixed for x86.
Powered by blists - more mailing lists