Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2372842imu; Wed, 21 Nov 2018 10:34:18 -0800 (PST) X-Google-Smtp-Source: AJdET5egbBzDgSJElYWKaIo3VxCY/TTwQAxQiq5yPmIsUyEJ9KL6xf336zRwBBsazUDunpCYxiN5 X-Received: by 2002:a63:f74f:: with SMTP id f15mr7040343pgk.190.1542825257973; Wed, 21 Nov 2018 10:34:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542825257; cv=none; d=google.com; s=arc-20160816; b=RT+P3+ZzjbjFLWM836JntyiCWWHvJSm4p9VH/NqAofdnWwGKhlssnjFByKZ9vBQ3ms liMN+uBd+A/4+5FYibT2ZomBHeW1vGg2OYG7uRMO0opjeP+Prud/EFvp8E3HDmLeXyN6 Kp4uAedrjCxUc4tDblrCFh3bUmgJ328pvxoo2Y612P8yB6B6zyO/E/RX8rgCFTiw+joU fR2CRly0BTBRr0Ws9bjfLjmp/6WwdkJ53OWLDOKaAI6Hajksq/vCIKh9HlJsQUXdIwYd kQcKSrdd2XlzNWS0yh0Jcdlap3AnbZNcnguXNczsCUu0RTV1hfQ5Pb05agjWm6zHraZC /oQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=rfKtE+2mHMXz5EI8SGJ6PfKiWDlLvp9kdfD1aeCC9io=; b=gM+XuPBnpAPytPCTv5NG2c56UkodeNT6Z/muYcMVwstf0hUhhnIBSoCBLbOQxi1QWR 8GA+NG3/Qz23+sW152hPMVsBU8hXOG4rMSbIdoa4hXZcehJqXWZCOUrEqiXxyBOZ9/9s c17ZqJZe4uQerBZc8P2VZRR/xr/I5ux8U3JPx9LDnLpCSZq0DZvcTZ0CoWZlOmzlold+ EI0ZISfUWIq914QNLjKEauKOW13iSeQOEs+FDyp8Py5Rua5i8uOb21uH7GyH1o2bdqXI LxV6w2XZ0efiOanXQ+iBpx5AZ6vCvrn7z7mo36X/EB4skjIecsDhZ9THeCbuAOCAmSCO +N0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=WOFCsNix; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cd16si20423431plb.47.2018.11.21.10.34.02; Wed, 21 Nov 2018 10:34:17 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=WOFCsNix; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731863AbeKVDO0 (ORCPT + 99 others); Wed, 21 Nov 2018 22:14:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:57780 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729859AbeKVDO0 (ORCPT ); Wed, 21 Nov 2018 22:14:26 -0500 Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id EC8F5214C1; Wed, 21 Nov 2018 16:39:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1542818356; bh=y3LFa2TrnCqDBLKbVOHe7YP7WgURDboAfp1yVTn9rXw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=WOFCsNix6RYJm9adVVTEpvJSRyLf2PyS7nBGgaq1wfWp+a9YzjbC0bCDbaUSK1v04 /AzHj3MiI+5hZmK1bLWpvEXCBoum/+TCaUPOHnqINIunh8zPNeepH/qoyHiEdTDByh sXaHNEv86B5qEobstRlX4iNX3rzf95YhOnyjqwLE= Received: by mail-qk1-f174.google.com with SMTP id o125so5267395qkf.3; Wed, 21 Nov 2018 08:39:15 -0800 (PST) X-Gm-Message-State: AA+aEWZCjBOMkxTVK0DDb5/JQ5N9XWbV1/y6U6FbBWjUcIyYFRZzl1hx cJsWj2BmXxg2adL59aYRNf0RI/pwypjuPKnHBg== X-Received: by 2002:a37:5686:: with SMTP id k128mr5915745qkb.29.1542818355174; Wed, 21 Nov 2018 08:39:15 -0800 (PST) MIME-Version: 1.0 References: <1542787873-8429-1-git-send-email-miles.chen@mediatek.com> In-Reply-To: <1542787873-8429-1-git-send-email-miles.chen@mediatek.com> From: Rob Herring Date: Wed, 21 Nov 2018 10:39:03 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC PATCH] of: make MAX_RESERVED_REGIONS configurable To: Miles Chen Cc: Frank Rowand , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 21, 2018 at 2:11 AM wrote: > > From: Miles Chen > > When we use more than 32 entries in /resered-memory, > there will be an error message: "not enough space all defined regions.". > We can increase MAX_RESERVED_REGIONS to fix this. > > commit 22f8cc6e3373 ("drivers: of: increase MAX_RESERVED_REGIONS to 32") > increased MAX_RESERVED_REGIONS to 32 but I'm not sure if increasing > MAX_RESERVED_REGIONS to 64 is suitable for everyone. > > In this RFC patch, CONFIG_MAX_OF_RESERVED_REGIONS is added and used as > MAX_RESERVED_REGIONS. Add a sanity test to make sure that > MAX_RESERVED_REGIONS is less than INIT_MEMBLOCK_REGIONS. > Users can configure CONFIG_MAX_OF_RESERVED_REGIONS according to their > need. I don't want a kconfig option for this. I think it should be dynamic instead. The current flow is like this: for each reserved node: - call memblock_reserve - Add info to reserved_mem array I think we should change it to: for each reserved node: - call memblock_reserve - count number of nodes Alloc array using memblock_alloc for each reserved node: - Add info to reserved_mem array Rob