Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1747363imm; Tue, 10 Jul 2018 07:16:56 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfM8BpAAgLErbCQaU4BeRciuFJ3g7XwLLToHq8R/FFkxrqxEpl0SzmgcXqVcqzIXWrnFJhK X-Received: by 2002:a63:4203:: with SMTP id p3-v6mr22864954pga.184.1531232216760; Tue, 10 Jul 2018 07:16:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531232216; cv=none; d=google.com; s=arc-20160816; b=QGVDwuXa7RauiMPviB9TX9gDLM/hfnLduU4VVGeklxNdBgvY5gE/Cld/EYYfcfGh+Q Pu30m/UkNshoEePqr8LItp4ABk/ZzFBdw1/Mt5LdBCkN2BQHjCBXeMHdOO9pYtQpZA0b vLSSF+mFo2HdQ1lkMriWkyZvifxdpzlr7FgaCN7f+TbCbAtbTTrDALdiCaHUrkzAP7Px WuvgtvLipNXyjPytxFlVz0MGDQ1zJ2gG5pxJ+TOJF/UPT1lQI57EYURH4hs+9/rjznxL LpYIcgIUPZaJeLHyNVuQSTxV4+jImid472koFL0ToeeyFr4wCoE4xLzoAolgz1bSC9or Tqdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=N+vNW8amPWm+22434h8q2J4+E8dpyO/X8yBkgJBvdOw=; b=CNZiHRXOiPNu9pArE+gstYnE3Gr9gfwbX/uRaAJsBWrrtmzbl52vLOEaAtvvaBDb6z MDqfX2gzXJF+glq93bFg2S7agc1mWWQ1eF0ApkO8VCGSz8fcqkekGLcCjl/HKrSXEDEQ uCDFbPvqXnfJ/UxM/f5V04P0/jyQbxHE2O/2uHTzsDeZaTbNv9IilarZ2N1SfVlnBGse N9S+HuKM9d8y9etdUzAGz7jdq8yeVc7zKXw6XNlWnnMo+8IVSTFEF7QC9m4y8CUqSAES JCT9QjfmjEo7IBgFeUFZA3f2Oglmil+X2gLkpUkGxHHtZOp/BB7AV6XjNGXI/kC+uho4 unjw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q2-v6si16715845plh.136.2018.07.10.07.16.41; Tue, 10 Jul 2018 07:16:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933552AbeGJOP5 (ORCPT + 99 others); Tue, 10 Jul 2018 10:15:57 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:47510 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754265AbeGJOP4 (ORCPT ); Tue, 10 Jul 2018 10:15:56 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 63D4880D; Tue, 10 Jul 2018 07:15:56 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 316CD3F589; Tue, 10 Jul 2018 07:15:56 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id E8E921AE53F3; Tue, 10 Jul 2018 15:16:37 +0100 (BST) Date: Tue, 10 Jul 2018 15:16:37 +0100 From: Will Deacon To: Arnd Bergmann Cc: Nikunj Kela , Catalin Marinas , xe-kernel@external.cisco.com, Linux Kernel Mailing List , Linux ARM Subject: Re: [PATCH v3] arm64: add ARM64-specific support for flatmem Message-ID: <20180710141637.GB9022@arm.com> References: <20180706174724.44594-1-nkela@cisco.com> <20180710130650.GD31318@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 10, 2018 at 03:25:14PM +0200, Arnd Bergmann wrote: > On Tue, Jul 10, 2018 at 3:06 PM, Will Deacon wrote: > > On Tue, Jul 10, 2018 at 02:55:41PM +0200, Arnd Bergmann wrote: > >> On Fri, Jul 6, 2018 at 7:47 PM, Nikunj Kela wrote: > >> > Flatmem is useful in reducing kernel memory usage. > >> > One usecase is in kdump kernel. We are able to save > >> > ~14M by moving to flatmem scheme. > >> > > >> > Cc: xe-kernel@external.cisco.com > >> > Cc: Nikunj Kela > >> > Signed-off-by: Nikunj Kela > >> > --- > >> > arch/arm64/Kconfig | 3 +++ > >> > 1 file changed, 3 insertions(+) > >> > > >> > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > >> > index 42c090c..f5b4c49 100644 > >> > --- a/arch/arm64/Kconfig > >> > +++ b/arch/arm64/Kconfig > >> > @@ -775,6 +775,9 @@ config ARCH_SPARSEMEM_DEFAULT > >> > config ARCH_SELECT_MEMORY_MODEL > >> > def_bool ARCH_SPARSEMEM_ENABLE > >> > > >> > +config ARCH_FLATMEM_ENABLE > >> > + def_bool y > >> > + > >> > config HAVE_ARCH_PFN_VALID > >> > def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM > >> > > >> > >> I'm getting hundreds of errors in randconfig builds with this: > > > > Damn, I was worried something like this might happen. Sorry! > > > > Does randconfig also fuzz CONFIG_EXPERT? We only added ARCH_FLATMEM_ENABLE > > so that people can hand-configure crashkernels to make them small; there will > > be plenty of situations where it's just going to cause more problems than it > > solves, so I'd be happy hiding it behind EXPERT if it helps. > > Yes, randconfig also tests EXPERT and COMPILE_TEST configurations, though I > don't test the !COMPILE_TEST ones myself, so you can also hide options from > me by making them 'depends on !COMPILE_TEST'. > > > Otherwise we can probably through a 'def_bool !NUMA' at it. > > Yes, I was going to send a patch with that next after testing it some more. > So far it's holding up. This is also what some other architectures have, so > it's probably safe. Ok, let's go with that then. If I don't see a patch from you in a day or two, I'll write one myself :) Will