Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5933058yba; Wed, 1 May 2019 02:51:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqzY3KEsDEq4rUZeeIO6UplhukpsiSd5YpjTcvbuIHsGWvH6nMaMjT+DLHYMdHM7EU4E6lD+ X-Received: by 2002:a62:5fc5:: with SMTP id t188mr26214871pfb.155.1556704266210; Wed, 01 May 2019 02:51:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556704266; cv=none; d=google.com; s=arc-20160816; b=MMfP+ttC7XuhK8Vucx0okVj7WEEAV3pf4DD1k1ypFujsSqGWjj0qrzmwU0jHxfgnpx e7ViOClGHHC+shh4gCl3uTbCLo0SICK1Q3lr2B4folQu5rY+lF/6ulrqekWSLu8rPLFH e2inzvbTo15BvN2xr8yWx0XFryOb3nPcW8DNvs8HGnMHJYA6p52IfSoV0p9rz3/qTdJL e+tjClXHxdth5igA9SBxHaEnJBCc2tFPrtYHUlhuW8M/kzbJzxNdMbWLyBtdlUDqyedX 23ZtVfUS/PsUVHPSXYgJbb5r1UjryQP4vRZMqtd9Zkfq5wL0GvNtrYtxL2Hacw020e7T hcEw== 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; bh=nRapfsuTHbK2OMDtbzoachnRGk6GQ0bVifbrf635oi8=; b=KVDRexGGfotcLObO1gsKt0WPRVclBNCEvT+qADaHnhiu5zML8XgrTgiHRhez6fYwBZ fLwnVLBS12vMotZv0EsYSurHJsJdSmCdXmw05/LBd3ZkdaUr//YDy9yGEETZ769f7GvK JswuHh+0lFCfeYhHIjGzkxWHkikFWNAd9vNsQiCHfHZuKQalT62HoelNtSR3cqNqKeIK w/+HIv5iA55zwhpxE46C512RsL39kG9syL/5osESuzpG5AgPuvFhuK5Xpp2hGAcA9qz7 fsvr1loQm2RbrkMwJ90eyrsS/b1O5G+pNoKRsGM88aSwKI11oC7k57YJKibkG/lJhk+A 9frw== 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 d37si39849764plb.401.2019.05.01.02.50.50; Wed, 01 May 2019 02:51:06 -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 S1726249AbfEAJuC (ORCPT + 99 others); Wed, 1 May 2019 05:50:02 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:57378 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726052AbfEAJuC (ORCPT ); Wed, 1 May 2019 05:50:02 -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 8BDAFA78; Wed, 1 May 2019 02:50:01 -0700 (PDT) Received: from e107155-lin (e107155-lin.cambridge.arm.com [10.1.196.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CE70D3F719; Wed, 1 May 2019 02:49:59 -0700 (PDT) Date: Wed, 1 May 2019 10:49:53 +0100 From: Sudeep Holla To: Sodagudi Prasad Cc: julien.thierry@arm.com, will.deacon@arm.com, catalin.marinas@arm.com, mark.rutland@arm.com, lorenzo.pieralisi@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Sudeep Holla Subject: Re: PSCI version 1.1 and SYSTEM_RESET2 Message-ID: <20190501094953.GA21851@e107155-lin> References: <24970f7101952f347bd4046c9a980473@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 30, 2019 at 05:07:31PM -0700, Sodagudi Prasad wrote: > On 2019-04-30 14:44, Sodagudi Prasad wrote: > +Sudeep > > > Hi Mark/Will, > > > > I would like to understand whether ARM linux community have plans to > > support PSCI version 1.1 or not. > > PSCI_1_1 specification introduced support for SYSTEM_RESET2 command > > and this new command helps mobile devices to SYSTEM_WARM_RESET > > support. Rebooting devices with warm reboot helps to capture the > > snapshot of the ram contents for post-mortem analysis. > > I think, there is a recent discussion from Sudeep for the SYSTEM_RESET2 > support. > https://patchwork.kernel.org/patch/10884345/ > This has landed in -next, and hopefully must appear in v5.2 > > Hi Sudeep, > > I was going through your discussion in the below list - > https://lore.kernel.org/lkml/d73d3580-4ec1-a281-4585-5c776fc08c79@xilinx.com/ > > There is no provision to set up reboot mode dynamically instead kernel > command line parameter. > Looking for options to reboot device with warm reboot option when kernel > crashed. > > panic() --> emergency_restart() --> machine_emergency_restart() --> > machine_restart(NULL); > > It would nice if there is a config option to reboot the device either in > warm or cold in the case of kernel panic. I presume you prefer to do warm boot in case of panic to get a dump of the memory to inspect ? If so, is kexec/kdump not the mechanism to achieve that ? I am just trying to understand the use case. Xilinx asked for the same but never got to understand their use case. -- Regards, Sudeep