Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6357174yba; Wed, 1 May 2019 10:37:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqxzzk3jfL8/v7dy1QeiByfwvzezfUowuhbun+jyxkdoDv6oys7rupvVH4/SUNNoKXp+9FrN X-Received: by 2002:aa7:92c4:: with SMTP id k4mr49492675pfa.183.1556732230938; Wed, 01 May 2019 10:37:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556732230; cv=none; d=google.com; s=arc-20160816; b=eVekQvE28mgiUaEOC5VwuwhetEAHcxKNuDS/t8+lzdmfARTOHPT87VfStbx8sinAgz e6Bsq0raHfeHXoFB1vSkqai8l+EHwZud3P+zRb5pfmrRpbNQE2WckKnT8l2/Thq+NpJD vaPtv00BjeOs+Uf+JF4LMoYKSpCSTVjm9pe2n5Mm5C8x8Ialsd4zn0thPsXVhvlsRPaJ SBirVNsXZLIAl6wshmH6sneHGfxdgvErXmMJCbKJnBYrZhk2nhRXReGtZqeJYVjynBVe xlEpDYHpc/8SJzdznFityVy3+7EErDA5C/ru2/SM+0LSokjB2NHLNViQsQ8wRQCixI8x VolA== 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=iz8nzjnh9CNeGFtSiGYYAKuZLQJbzOX1S+iE4TuGqgQ=; b=mB5S+E/HK79NK9Syvvs3KBjqkDTpk9Un+rPJ1ALmPPPnA/7mCmuIQ3UbNZpxyGZgzu PKl95wod1x0sxTfKOkXKH/mEGVEXoc9vqMzzfc0AzdgWV5INSUwxeodyT+fXc2WeAwRx Y/AXKod7EwsgrFI4wExqPifFwEAkjUSSybuSSMEoYTQmwmwRHkNGrAqqWsuNlxI7/sn1 N9Acx0KYyczy06o6ocrx9XUdMN8I5vqPn1T1J24tflkhGLo+5vDmV2yeM/mLk0rjrich m+ugxGcwGpAnUY7+IudBPyvZWiGzDQbT4KckxiF+k/cH+8Hep7MRkFyTH8Dg/Bz1rYbU DKxw== 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 o70si42486423pfa.33.2019.05.01.10.36.54; Wed, 01 May 2019 10:37:10 -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 S1726229AbfEARfc (ORCPT + 99 others); Wed, 1 May 2019 13:35:32 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:34486 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726019AbfEARfb (ORCPT ); Wed, 1 May 2019 13:35:31 -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 2382780D; Wed, 1 May 2019 10:35:31 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B2DEA3F719; Wed, 1 May 2019 10:35:29 -0700 (PDT) Date: Wed, 1 May 2019 18:35:27 +0100 From: Mark Rutland To: Anup Patel Cc: Atish Patra , Palmer Dabbelt , "aou@eecs.berkeley.edu" , "linux-kernel@vger.kernel.org" , "zong@andestech.com" , "linux-riscv@lists.infradead.org" Subject: Re: [PATCH] RISC-V: Add an Image header that boot loader can parse. Message-ID: <20190501173526.GH11740@lakrids.cambridge.arm.com> References: <20190501170053.GG11740@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 01, 2019 at 10:41:52PM +0530, Anup Patel wrote: > On Wed, May 1, 2019 at 10:30 PM Mark Rutland wrote: > > > > On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote: > > > On 4/29/19 4:40 PM, Palmer Dabbelt wrote: > > > > On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.patra@wdc.com wrote: > > > > > Currently, last stage boot loaders such as U-Boot can accept only > > > > > uImage which is an unnecessary additional step in automating boot flows. > > > > > > > > > > Add a simple image header that boot loaders can parse and directly > > > > > load kernel flat Image. The existing booting methods will continue to > > > > > work as it is. > > > > > > > > > > Tested on both QEMU and HiFive Unleashed using OpenSBI + U-Boot + Linux. > > > > > > > > > > Signed-off-by: Atish Patra > > > > > --- > > > > > arch/riscv/include/asm/image.h | 32 ++++++++++++++++++++++++++++++++ > > > > > arch/riscv/kernel/head.S | 28 ++++++++++++++++++++++++++++ > > > > > 2 files changed, 60 insertions(+) > > > > > create mode 100644 arch/riscv/include/asm/image.h > > > > > > > > > > diff --git a/arch/riscv/include/asm/image.h b/arch/riscv/include/asm/image.h > > > > > new file mode 100644 > > > > > index 000000000000..76a7e0d4068a > > > > > --- /dev/null > > > > > +++ b/arch/riscv/include/asm/image.h > > > > > @@ -0,0 +1,32 @@ > > > > > +/* SPDX-License-Identifier: GPL-2.0 */ > > > > > + > > > > > +#ifndef __ASM_IMAGE_H > > > > > +#define __ASM_IMAGE_H > > > > > + > > > > > +#define RISCV_IMAGE_MAGIC "RISCV" > > > > > + > > > > > +#ifndef __ASSEMBLY__ > > > > > +/* > > > > > + * struct riscv_image_header - riscv kernel image header > > > > > + * > > > > > + * @code0: Executable code > > > > > + * @code1: Executable code > > > > > + * @text_offset: Image load offset > > > > > + * @image_size: Effective Image size > > > > > + * @reserved: reserved > > > > > + * @magic: Magic number > > > > > + * @reserved: reserved > > > > > + */ > > > > > + > > > > > +struct riscv_image_header { > > > > > + u32 code0; > > > > > + u32 code1; > > > > > + u64 text_offset; > > > > > + u64 image_size; > > > > > + u64 res1; > > > > > + u64 magic; > > > > > + u32 res2; > > > > > + u32 res3; > > > > > +}; > > > > > > > > I don't want to invent our own file format. Is there a reason we can't just > > > > use something standard? Off the top of my head I can think of ELF files and > > > > multiboot. > > > > > > Additional header is required to accommodate PE header format. Currently, > > > this is only used for booti command but it will be reused for EFI headers as > > > well. Linux kernel Image can pretend as an EFI application if PE/COFF header > > > is present. This removes the need of an explicit EFI boot loader and EFI > > > firmware can directly load Linux (obviously after EFI stub implementation > > > for RISC-V). > > > > Adding the EFI stub on arm64 required very careful consideration of our > > Image header and the EFI spec, along with the PE/COFF spec. > > > > For example, to be a compliant PE/COFF header, the first two bytes of > > your kernel image need to be "MZ" in ASCII. On arm64 we happened to find > > a valid instruction that we could rely upon that met this requirement... > > The "MZ" ASCII (i.e. 0x5a4d) is "li s4,-13" instruction in RISC-V so this > modifies "s4" register which is pretty harmless from Linux RISC-V booting > perspective. > > Of course, we should only add "MZ" ASCII in Linux RISC-V image header > when CONFIG_EFI is enabled (just like Linux ARM64). Great. It would probably be worth just mentioning that in the commit message, so that it's clear that has been considered. Thanks, Mark.