From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6DF7C3A5A9 for ; Thu, 5 Sep 2019 03:15:35 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7090D20820 for ; Thu, 5 Sep 2019 03:15:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7090D20820 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 46P5RQ71BpzDqlQ for ; Thu, 5 Sep 2019 13:15:30 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 46P5P45FXRzDqrs for ; Thu, 5 Sep 2019 13:13:28 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix) id 46P5P241YNz9sDB; Thu, 5 Sep 2019 13:13:26 +1000 (AEST) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 46P5P16CkHz9s3Z; Thu, 5 Sep 2019 13:13:25 +1000 (AEST) From: Michael Ellerman To: Hari Bathini , linuxppc-dev Subject: Re: [PATCH v5 15/31] powernv/fadump: support copying multiple kernel boot memory regions In-Reply-To: References: <156630261682.8896.3418665808003586786.stgit@hbathini.in.ibm.com> <156630275779.8896.7854485220030978790.stgit@hbathini.in.ibm.com> <877e6oqoxm.fsf@mpe.ellerman.id.au> Date: Thu, 05 Sep 2019 13:13:25 +1000 Message-ID: <87k1anph9m.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ananth N Mavinakayanahalli , Mahesh J Salgaonkar , Vasant Hegde , Oliver , Nicholas Piggin , Daniel Axtens Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Hari Bathini writes: > On 04/09/19 5:00 PM, Michael Ellerman wrote: >> Hari Bathini writes: >>> Firmware uses 32-bit field for region size while copying/backing-up >> >> Which firmware exactly is imposing that limit? > > I think the MDST/MDRT tables in the f/w. Vasant, which component is that? > >>> + /* >>> + * Firmware currently supports only 32-bit value for size, >> >> "currently" implies it could change in future? >> >> If it does we assume it will only increase, and we're happy that old >> kernels will continue to use the 32-bit limit? > > I am not aware of any plans to make it 64-bit. Let me just say f/w supports > only 32-bit to get rid of that ambiguity.. OK. As long as everyone is aware that the kernel has no support for it increasing it, without code changes. cheers