Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp799355imm; Tue, 15 May 2018 09:19:46 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqIHm/SVO8rUZOvZSiR08KIXRirAq4LE2+Hx0aEogshGOzTOqkXEKaXQL6/7hNoXZN2+xDX X-Received: by 2002:a17:902:b087:: with SMTP id p7-v6mr15117339plr.227.1526401186284; Tue, 15 May 2018 09:19:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526401186; cv=none; d=google.com; s=arc-20160816; b=sqX23GQPLYWZZix4paBmWshR6SLIQD13SE1q1gcDU3sI6x8Ow+zSxBcMdM0MO5hMu9 ec7mKIgpAHZTouT98RPtwB+RkIdvD1fzQKrLzSjZnEsSN7peeeMvOmwpKUWGJhqH6wFk Ula0MmJr6ogRLYpJUSkSDd9SRjyc92NW9CH1gTVKPaTc6A3/BvHkEVuKwWDWkd3CedLO 6hvJfmxnjFrM8efK0WMxWY01nKqkHs99I3yCxSjBtozRRiCQLsLdur6o+0g+6XNlT4Nf B8ulFkjtVA/cn1IKkUbgSJQBLPpK4DJ1FuEmDCkNM6MjYJTQ4wZnMA+7MqBG0NyRvCkh e+eA== 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:cc:from:references:to:subject:arc-authentication-results; bh=oSYeG9JWaGvdhf+U4PfqNix8sNojDWJeCVSjL5szpnw=; b=XVFNZThNQk3KMIPZbgKTFKepukS9kOmf9Idud/7Z1y2d0dz12FtwVT8+aTVYWklIfd /BovXLCmgnp7aoSnYzNBEFgrk98xxSP5AhUI2dmiLmIWezRLaFYDePRNUD6aA5RgLf2m VWe9RU5O9WT6Bnxx72Dn6DcNNzbk/KzMVtKofvlnVoTFF8ecVAp5pbjSr4nodkqBYr6M GfnA4s1s0tcbUXF0OyZ+l/084snP9I+45TbdPUOOKZ73evI/805TJTEEg30081Kid0Rm 3hu10j47o+EhSHrV3Rb9dhARgPqIegiEC+OW95i3iFr9yM6hngydUEloCp7f4JwLO6DX +GQA== 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 e12-v6si317898pgn.155.2018.05.15.09.19.31; Tue, 15 May 2018 09:19:46 -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 S1752253AbeEOQTB (ORCPT + 99 others); Tue, 15 May 2018 12:19:01 -0400 Received: from foss.arm.com ([217.140.101.70]:35086 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751219AbeEOQTA (ORCPT ); Tue, 15 May 2018 12:19:00 -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 214B31529; Tue, 15 May 2018 09:19:00 -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 A067A3F53D; Tue, 15 May 2018 09:18:54 -0700 (PDT) Subject: Re: [PATCH v9 03/11] arm64: kexec_file: invoke the kernel without purgatory To: AKASHI Takahiro References: <20180425062629.29404-1-takahiro.akashi@linaro.org> <20180425062629.29404-4-takahiro.akashi@linaro.org> <9c830fe8-56d8-b43a-6265-43d31dffe61a@arm.com> <20180507052208.GD11326@linaro.org> <20180515044542.GC2737@linaro.org> From: James Morse 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 Message-ID: Date: Tue, 15 May 2018 17:15:52 +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: <20180515044542.GC2737@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 15/05/18 05:45, AKASHI Takahiro wrote: > On Fri, May 11, 2018 at 06:03:49PM +0100, James Morse wrote: >> On 07/05/18 06:22, AKASHI Takahiro wrote: >>> On Tue, May 01, 2018 at 06:46:06PM +0100, James Morse wrote: >>>> On 25/04/18 07:26, AKASHI Takahiro wrote: >>>>> 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) >> >>>>> 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 >> >> >>>> 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). >>> >>> The problem is arch.dtb_mem is currently defined only if CONFIG_KEXEC_FILE. >> >> I thought it was ARCH_HAS_KIMAGE_ARCH, which we can define all the time if >> that's what we want. >> >> >>> So I would like to >>> - merge this patch with patch#8 >>> - change the condition >>> #ifdef CONFIG_KEXEC_FILE >>> kimage->file_mode ? kimage->arch.dtb_mem : 0); >>> #else >>> 0); >>> #endif >> >> If we can avoid even this #ifdef by always having kimage->arch, I'd prefer that. >> If we do that 'dtb_mem' would need some thing that indicates its for kexec_file, >> as kexec has a DTB too, we just don't know where it is... > > OK, but I want to have a minimum of kexec.arch always exist. I'm curious, why? Its 32bytes that is allocated a maximum of twice. (my questions on what needs to go in there were because it looked like a third user was missing...) > How about this? > > | struct kimage_arch { > | phys_addr_t dtb_mem; > | #ifdef CONFIG_KEXEC_FILE #ifdef in structs just breeds more #ifdefs, as the code that accesses those members has to be behind the same set of conditions. Given this, I prefer the #ifdefs around cpu_soft_restart() as it doesn't force us to add more #ifdefs later. For either option without purgatory_info: Reviewed-by: James Morse Thanks, James