From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752197AbeAWTgN (ORCPT ); Tue, 23 Jan 2018 14:36:13 -0500 Received: from mail-lf0-f65.google.com ([209.85.215.65]:37584 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751964AbeAWTgM (ORCPT ); Tue, 23 Jan 2018 14:36:12 -0500 X-Google-Smtp-Source: AH8x2249XWqJVkFqpR9yv5NZMS3YUonbX7WufdPREa6YtWSw0x4XmIKpBSHGSY9dsuW+d8tQvzxCAg== Date: Tue, 23 Jan 2018 22:36:23 +0300 From: Serge Semin To: Jiaxun Yang Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 12/14] MIPS: memblock: Discard bootmem from Loongson3 code Message-ID: <20180123193623.GC28147@mobilestation> References: <20180117222312.14763-1-fancer.lancer@gmail.com> <20180117222312.14763-13-fancer.lancer@gmail.com> <1516746524.20678.6.camel@flygoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1516746524.20678.6.camel@flygoat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Jiaxun, On Tue, Jan 23, 2018 at 10:28:44PM +0000, Jiaxun Yang wrote: > 在 2018-01-18四的 01:23 +0300，Serge Semin写道： > Hi Serge > > > Loongson64/3 runs its own code to initialize memory allocator in > > case of NUMA configuration is selected. So in order to move to the > > pure memblock utilization we discard the bootmem allocator usage > > and insert the memblock reservation method for > > kernel/addrspace_offset > > memory regions. > > Thanks for your patch. However, In my test, the system didn't boot > anymore with your patch. Since I don't have any lowlevel debug > instuments(ejtag or something). I can't provide any detail about the > problem. Just let you know that we have a problem here. > Thanks for performing the tests of the patchset. I really appreciate this. Regarding the problems you got. You must be doing something wrong, since Matt Redfearn already did the tests on Loongson3: https://lkml.org/lkml/2018/1/22/610 and the kernel turns out to be booting without troubles. So could you make sure, that you did everything right? Particularly, you said the patch (singular) isn't working. But this patch functionality depends on the whole patchset. Did you apply all the patches I sent and fully rebuild the kernel then? Regards, -Sergey > > -- > Jiaxun Yang