Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2735016pxb;
        Mon, 31 Jan 2022 03:12:19 -0800 (PST)
X-Google-Smtp-Source: ABdhPJyRjzjpGETYzRAKHhX4P6xePFoYiZaVSol4V0/m+SFkNefsZrZuCTSnhyUEUJqjyiQxgtb9
X-Received: by 2002:a17:90a:2c0a:: with SMTP id m10mr33532396pjd.183.1643627538686;
        Mon, 31 Jan 2022 03:12:18 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1643627538; cv=none;
        d=google.com; s=arc-20160816;
        b=aRjhIDhMmMHgmNARFZSTCeL9rf22iXsqAYi91723yNohZlfTRnMeuGrWVB2y/250jV
         9DhnhV50F92DIuQiZrKY2JNdVphSOk7yucdDsLrdKfH8KLwesD3PUdg44k0z1znVnU2/
         +N6hZuGqaedCPz5mKQz7VtOtcznih0UucTnbCxqjIMoUsefVmk0NaNXK99LmPg2GrFAM
         HbhJpRFbRRB7vt3goK5ibpP4RPL4cM896y/FvwbhPOOVwvfJV0m/NwzrMkFsdxUE7Kv1
         5aM0IoK2IyxwWfxbKjiUEEnql4wSdJOr/XF7e05IiS3v1RWh2/a12SXUCuzESeq7gU2t
         NZVA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:dkim-signature;
        bh=MAhtffWLvTb95O1nHiMgqFD+X4oKL17RAdXD+wioaRg=;
        b=q8UUC5qa6ThNJUPQBOIA+B6Pr9frDa8Hai388DMnpp1cCmyudUksV8/YRHCRMD37a1
         SFBdCP3YVo9fHhzRsEbbokm+zdPmPsZOFZj1kGNCDC3ifBpvsNCKX+hOwasK4B/EtwR7
         WU/mkEfqX6epkeQjMWnn4kvEYab69EIyePU5IhkD179noU55hGQW1G1hIU7TMaay1V/T
         06OpLubxc09N2FgUePdUnpPXEb1qMSBOAgBsgRyfW0/1iRBOk6Yfu2lvoMXbyc+/n0GW
         FXxkISBVVu6S2qvmwTdZ+cGaZu+Jt4M1XsRZZCa2zTrESNOBB5+UDlTDc0/3cS3hQUbZ
         CQIQ==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@kernel.org header.s=k20201202 header.b=One52MfB;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id l22si13501153pfc.103.2022.01.31.03.12.07;
        Mon, 31 Jan 2022 03:12:18 -0800 (PST)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@kernel.org header.s=k20201202 header.b=One52MfB;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1349185AbiA1PdO (ORCPT <rfc822;sshegde.linux@gmail.com>
        + 99 others); Fri, 28 Jan 2022 10:33:14 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57860 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229871AbiA1PdN (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 28 Jan 2022 10:33:13 -0500
Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2236CC061714;
        Fri, 28 Jan 2022 07:33:13 -0800 (PST)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by dfw.source.kernel.org (Postfix) with ESMTPS id B4DF460ECE;
        Fri, 28 Jan 2022 15:33:12 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 206B7C340E0;
        Fri, 28 Jan 2022 15:33:12 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1643383992;
        bh=MAhtffWLvTb95O1nHiMgqFD+X4oKL17RAdXD+wioaRg=;
        h=References:In-Reply-To:From:Date:Subject:To:Cc:From;
        b=One52MfBvMSDWvTWPac78/g+BCnPDSWcAb1PUw8N14XImZpuNJ1/p9CFB8eXb8tZv
         tg4ShPYSt3qts2nvMDLMYGSsSn/DnXvfxu9cdBcrU6ixNKadN7JG67zd6voHZwBR2u
         uf0aixlfSsaVzScOtGohS1rXjFaVSYm+a2N6rEz7qLfUjPpOHII3CLRIAbaShHjfUI
         rt10bKA1dL4lH4nQuOj7hOzNr6hpbUEKB8MCUEHJryNf22y02QBt34QAboS7ip5a+C
         fcabLaZVOWLMYDM3og08Vf7E0QaAHQtVwf7QYEm2YRYaYUwWvM8oF66cY6/W7Z2r6c
         K/07gBUPvtQyw==
Received: by mail-qk1-f175.google.com with SMTP id g145so5853090qke.3;
        Fri, 28 Jan 2022 07:33:12 -0800 (PST)
X-Gm-Message-State: AOAM530aMM+/AqfH2GzETyIsPUcgBf9FqY1sHaxSB2Zbzk1PnZPMbeCA
        I9If/+OhZlgFWe8DIb0OM2cSb597msKIint9lg==
X-Received: by 2002:a05:620a:4149:: with SMTP id k9mr6154130qko.323.1643383991204;
 Fri, 28 Jan 2022 07:33:11 -0800 (PST)
MIME-Version: 1.0
References: <20220128042321.15228-1-nikhil.gupta@nxp.com>
In-Reply-To: <20220128042321.15228-1-nikhil.gupta@nxp.com>
From:   Rob Herring <robh+dt@kernel.org>
Date:   Fri, 28 Jan 2022 09:32:59 -0600
X-Gmail-Original-Message-ID: <CAL_JsqKWmnQde+4tnZ3d90pWguezLVqto4DRe3WRjf9PCQ=L4w@mail.gmail.com>
Message-ID: <CAL_JsqKWmnQde+4tnZ3d90pWguezLVqto4DRe3WRjf9PCQ=L4w@mail.gmail.com>
Subject: Re: [PATCH] of/fdt: move elfcorehdr reservation early for crash dump kernel
To:     nikhil.gupta@nxp.com
Cc:     linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        Frank Rowand <frowand.list@gmail.com>,
        devicetree@vger.kernel.org,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Priyanka Jain <priyanka.jain@nxp.com>,
        Dong Aisheng <aisheng.dong@nxp.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 27, 2022 at 10:23 PM <nikhil.gupta@nxp.com> wrote:
>
> From: Nikhil Gupta <nikhil.gupta@nxp.com>
>
> elfcorehdr_addr is fixed address passed to Second kernel which may be conflicted
> with potential reserved memory in Second kernel,so fdt_reserve_elfcorehdr() ahead
> of fdt_init_reserved_mem() can relieve this situation.

How does changing the order help exactly? If you have an overlap, that
seems bad no matter what. What if the overlapping reserved area is
used by another core or firmware?

Rob