Received: by 10.192.165.148 with SMTP id m20csp5208049imm; Tue, 1 May 2018 10:50:06 -0700 (PDT) X-Google-Smtp-Source: AB8JxZorqjIA7zKJPGlFsmOxcaOrWGWbG+XDOMTRPTmiIAs+KRHVjGSR7GZshQ/NV6U6yzKNLwNI X-Received: by 10.167.130.208 with SMTP id f16mr1923253pfn.199.1525197006433; Tue, 01 May 2018 10:50:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525197006; cv=none; d=google.com; s=arc-20160816; b=pLlWRrjKmDfZId8YzfVnvxH61zfmawhkv9OBJ+SIGD1eFvDqELSjaTrhuV/RQ5mIIo dhw497Ee+vBvlpJ+U1xRsiNc8c5Ot7Q0OWgPX0KI0Sqk3EsR4h8+wzF0vnvZeRk7NoD/ rmxLWpv7MlnV7sCDYrb9NqUEEeM90Cg1WggIlrNt2mqq+iR85uoIfFAMeNFL/Bi+kJy0 frFUAu0Ak6AyREGfrGGESVGZi86Qqz3AR4XJ4XgKm9dktL0WXEdqxtYtg7LpqpNRVOSi y3E1QFKP97niydbEcbg99Rb/C6LIuIlxriPpKz+bx/iG2ZlmjoMauiNaRX5EBhe0GCL4 74NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=yPqu0LuFJxMaP3fJQASRNVyIlZOOhC4xo2qCOQJhhhE=; b=tXOP6oJU8rkmU+iDpNtgc371FcNN99q8EOhslsKIS1rrDOytuRrWBxOTJTeBmnE2bT sXKTpOXa4DdTbSEF4ijsy/2R4chlhDDd0rXf5M1o/2rE2kIq1B1YRXt3mamjnAbwPaYl xLTQSvE4RiPpydnygPsSoHR4S2vnnD3qJrJkYv1vIKr2AizGFd+6qnaPT/GGx/eat8rz hQkilImg29bm+jSetXGo2B/HGlQxJaJ3FroU6Shu44zKpnovo58FanbVQFCXjXlbmXLw ZgV2UOafmumwHT45tRnZ1G0fVlm1LWensBEgkujKUV79x/1nMFytx26pPmaCeqNI6MuU Q2Dg== 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 p1si9907535pfp.72.2018.05.01.10.49.52; Tue, 01 May 2018 10:50: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 S1756315AbeEARtJ (ORCPT + 99 others); Tue, 1 May 2018 13:49:09 -0400 Received: from foss.arm.com ([217.140.101.70]:49902 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756290AbeEARtH (ORCPT ); Tue, 1 May 2018 13:49:07 -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 A57F915AB; Tue, 1 May 2018 10:49:06 -0700 (PDT) Received: from [10.1.207.55] (melchizedek.cambridge.arm.com [10.1.207.55]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2168B3F5AF; Tue, 1 May 2018 10:49:02 -0700 (PDT) Subject: Re: [PATCH v9 03/11] arm64: kexec_file: invoke the kernel without purgatory To: AKASHI Takahiro Cc: catalin.marinas@arm.com, will.deacon@arm.com, dhowells@redhat.com, vgoyal@redhat.com, herbert@gondor.apana.org.au, davem@davemloft.net, dyoung@redhat.com, bhe@redhat.com, arnd@arndb.de, ard.biesheuvel@linaro.org, bhsharma@redhat.com, kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20180425062629.29404-1-takahiro.akashi@linaro.org> <20180425062629.29404-4-takahiro.akashi@linaro.org> From: James Morse Message-ID: <9c830fe8-56d8-b43a-6265-43d31dffe61a@arm.com> Date: Tue, 1 May 2018 18:46:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180425062629.29404-4-takahiro.akashi@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Akashi, On 25/04/18 07:26, AKASHI Takahiro wrote: > On arm64, purugatory would do almosty nothing. So just invoke secondary > kernel directy by jumping into its entry code. (Nits: purgatory, almost, directly) > While, in this case, cpu_soft_restart() must be called with dtb address > in the fifth argument, the behavior still stays compatible with kexec_load > case as long as the argument is null. > diff --git a/arch/arm64/kernel/cpu-reset.S b/arch/arm64/kernel/cpu-reset.S > index 8021b46c9743..391df91328ac 100644 > --- a/arch/arm64/kernel/cpu-reset.S > +++ b/arch/arm64/kernel/cpu-reset.S > @@ -24,9 +24,9 @@ > * > * @el2_switch: Flag to indicate a swich to EL2 is needed. (Nit: switch) > * @entry: Location to jump to for soft reset. > - * arg0: First argument passed to @entry. > - * arg1: Second argument passed to @entry. > - * arg2: Third argument passed to @entry. > + * arg0: First argument passed to @entry. (relocation list) > + * arg1: Second argument passed to @entry.(physcal kernel entry) (Nit: physical) > + * arg2: Third argument passed to @entry. (physical dtb address) > * > * Put the CPU into the same state as it would be if it had been reset, and > * branch to what would be the reset vector. It must be executed with the > diff --git a/arch/arm64/kernel/machine_kexec.c b/arch/arm64/kernel/machine_kexec.c > index f76ea92dff91..f7dbba00be10 100644 > --- a/arch/arm64/kernel/machine_kexec.c > +++ b/arch/arm64/kernel/machine_kexec.c > @@ -205,10 +205,17 @@ void machine_kexec(struct kimage *kimage) > * uses physical addressing to relocate the new image to its final > * position and transfers control to the image entry point when the > * relocation is complete. > + * In case of kexec_file_load syscall, we directly start the kernel, > + * skipping purgatory. We're not really skipping purgatory, purgatory doesn't exist! For regular kexec the image/payload we run is up to kexec-tools. For kexec_file_load its a kernel-image. Purgatory is a kexec-tools-ism. > cpu_soft_restart(kimage != kexec_crash_image, > - reboot_code_buffer_phys, kimage->head, kimage->start, 0); > + reboot_code_buffer_phys, kimage->head, kimage->start, > +#ifdef CONFIG_KEXEC_FILE > + kimage->purgatory_info.purgatory_buf ? > + 0 : kimage->arch.dtb_mem); > +#else > + 0); > +#endif Where does kimage->arch.dtb_mem come from? This patch won't build until patch 8 adds the config option, which is going to make bisecting any kexec side-effects tricky. purgatory_buf seems to only be set in kexec_purgatory_setup_kbuf(), called from kexec_load_purgatory(), which we don't use. How does this get a value? Would it be better to always use kimage->arch.dtb_mem, and ensure that is 0 for regular kexec (as we can't know where the dtb is)? (image_arg may then be a better name). Thanks, James