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;
Date:   Wed, 7 Apr 2021 11:29:27 -0500
From:   Rob Herring <robh@kernel.org>
To:     Nick Kossifidis <mick@ics.forth.gr>
Cc:     linux-riscv@lists.infradead.org, palmer@dabbelt.com,
        paul.walmsley@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] RISC-V: Add kexec/kdump support
Message-ID: <20210407162927.GA3836121@robh.at.kernel.org>
References: <20210405085712.1953848-1-mick@ics.forth.gr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210405085712.1953848-1-mick@ics.forth.gr>
Precedence: bulk

On Mon, Apr 05, 2021 at 11:57:07AM +0300, Nick Kossifidis wrote:
> This patch series adds kexec/kdump and crash kernel
> support on RISC-V. For testing the patches a patched
> version of kexec-tools is needed (still a work in
> progress) which can be found at:
> 
> https://riscv.ics.forth.gr/kexec-tools-patched.tar.xz
> 
> v3:
>  * Rebase on newer kernel tree
>  * Minor cleanups
>  * Split UAPI changes to a separate patch
>  * Improve / cleanup init_resources
>  * Resolve Palmer's comments
> 
> v2:
>  * Rebase on newer kernel tree
>  * Minor cleanups
>  * Properly populate the ioresources tre, so that it
>    can be used later on for implementing strict /dev/mem
>  * Use linux,usable-memory on /memory instead of a new binding

Where? In any case, that's not going to work well with EFI support 
assuming like arm64, 'memory' is passed in UEFI structures instead of 
DT. That's why there's now a /chosen linux,usable-memory-ranges 
property. 

Isn't the preferred kexec interface the file based interface? I'd 
expect a new arch to only support that. And there's common kexec DT 
handling for that pending for 5.13.

Rob