From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8445BC352A4 for ; Fri, 7 Feb 2020 11:09:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 554E1217BA for ; Fri, 7 Feb 2020 11:09:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="bBYKRJEQ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726798AbgBGLJz (ORCPT ); Fri, 7 Feb 2020 06:09:55 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:48194 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726674AbgBGLJz (ORCPT ); Fri, 7 Feb 2020 06:09:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581073794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SCntgRDrXOkiD6uxO1AkQeRXwRIwbg4qjS/12HTChTM=; b=bBYKRJEQc7qRMeFHuO1GouMOJPyjwEA/aZZxEimOjP1cBf4nPxbRqWg1VPe3n31JrrQUpF Yom6SVANzY0YKTX1BPEg0bL1NaEeOtcKcN39AecXll1w6sW0CitzYx9S/2R14mEE1WfVXh gJTzMO5KTSbvsJalR20rOGRg6U6I8HU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-256-Z5R0xcXuMqK-E4vfKKJ61A-1; Fri, 07 Feb 2020 06:09:50 -0500 X-MC-Unique: Z5R0xcXuMqK-E4vfKKJ61A-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1C5631005513; Fri, 7 Feb 2020 11:09:49 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-117-138.ams2.redhat.com [10.36.117.138]) by smtp.corp.redhat.com (Postfix) with ESMTP id BBF4A60BF7; Fri, 7 Feb 2020 11:09:46 +0000 (UTC) Subject: Re: [PATCH 1/2] efi/libstub: add support for loading the initrd from a device path To: Ard Biesheuvel , Heinrich Schuchardt Cc: Ard Biesheuvel , linux-efi , linux-arm-kernel , Leif Lindholm , Peter Jones , Matthew Garrett , Alexander Graf , Ilias Apalodimas , Daniel Kiper References: <20200206140352.6300-1-ardb@kernel.org> <20200206140352.6300-2-ardb@kernel.org> From: Laszlo Ersek Message-ID: Date: Fri, 7 Feb 2020 12:09:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-efi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-efi@vger.kernel.org On 02/06/20 23:35, Ard Biesheuvel wrote: > On Thu, 6 Feb 2020 at 18:26, Heinrich Schuchardt wrote: >> When booting via GRUB it will be GRUB knowing which initrd to load. >> > > Exactly, which is why GRUB will implement this protocol. That way, it > does not have to touch the DT at all, or create a bootparams struct > from setup data and inspect the various flags about placement, > alignment, preferred addresses, etc. > >> Please, indicate which software you expect to expose the initrd related >> EFI_LOAD_FILE2_PROTOCOL. >> > > The primary use case is GRUB and other intermediate loaders, since it > would remove any need for these components to know any such details. > My aim is to make the next architecture that gets added to GRUB for > EFI boot 100% generic. Understood, thanks. It sounds plausible to me. Laszlo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA1BEC352A2 for ; Fri, 7 Feb 2020 11:10:21 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7CB3A214AF for ; Fri, 7 Feb 2020 11:10:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="H89Flyp9"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="bBYKRJEQ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7CB3A214AF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wsKCg9BmLCBbJnKFzGCDRhjR726RjV/3bgjvclPj84Y=; b=H89Flyp9GfJO8e MuzpVYJU/cfEgXvelW1HUvZDsIsunHSocbDfrvj55HBjqq/tQ6P2cykSvjq1Zmu+z/qYdRfKVfINS tNzLfw4MhLeV4lICeHvxMCucJGr8RKpQGk1iMCffawZIVPUX4nZHcU1EOfsNqK2Zbd6DUIk8XrSJI B3/FtTORd3m9bt3H9uS9ERy++/O3JpmvPDbIWx6Qp3baD6/SiTozEyCsMqfgsC5Vmzq3ahT4OIGFP b4RUYxidEku56yA1dAqebG7GO5dJ7Nalg8dJ/A5TjEaHombQzId1Z8PDSxFmmyDA7kJcWewDnGggz ONc/x27L3xASz1ci2ksw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1j01Wa-000873-BH; Fri, 07 Feb 2020 11:10:16 +0000 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120] helo=us-smtp-1.mimecast.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j01WF-0006Zu-DE for linux-arm-kernel@lists.infradead.org; Fri, 07 Feb 2020 11:09:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581073794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SCntgRDrXOkiD6uxO1AkQeRXwRIwbg4qjS/12HTChTM=; b=bBYKRJEQc7qRMeFHuO1GouMOJPyjwEA/aZZxEimOjP1cBf4nPxbRqWg1VPe3n31JrrQUpF Yom6SVANzY0YKTX1BPEg0bL1NaEeOtcKcN39AecXll1w6sW0CitzYx9S/2R14mEE1WfVXh gJTzMO5KTSbvsJalR20rOGRg6U6I8HU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-256-Z5R0xcXuMqK-E4vfKKJ61A-1; Fri, 07 Feb 2020 06:09:50 -0500 X-MC-Unique: Z5R0xcXuMqK-E4vfKKJ61A-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1C5631005513; Fri, 7 Feb 2020 11:09:49 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-117-138.ams2.redhat.com [10.36.117.138]) by smtp.corp.redhat.com (Postfix) with ESMTP id BBF4A60BF7; Fri, 7 Feb 2020 11:09:46 +0000 (UTC) Subject: Re: [PATCH 1/2] efi/libstub: add support for loading the initrd from a device path To: Ard Biesheuvel , Heinrich Schuchardt References: <20200206140352.6300-1-ardb@kernel.org> <20200206140352.6300-2-ardb@kernel.org> From: Laszlo Ersek Message-ID: Date: Fri, 7 Feb 2020 12:09:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200207_030955_525542_12362526 X-CRM114-Status: GOOD ( 15.19 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-efi , Alexander Graf , Daniel Kiper , Ilias Apalodimas , Matthew Garrett , Peter Jones , Leif Lindholm , Ard Biesheuvel , linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 02/06/20 23:35, Ard Biesheuvel wrote: > On Thu, 6 Feb 2020 at 18:26, Heinrich Schuchardt wrote: >> When booting via GRUB it will be GRUB knowing which initrd to load. >> > > Exactly, which is why GRUB will implement this protocol. That way, it > does not have to touch the DT at all, or create a bootparams struct > from setup data and inspect the various flags about placement, > alignment, preferred addresses, etc. > >> Please, indicate which software you expect to expose the initrd related >> EFI_LOAD_FILE2_PROTOCOL. >> > > The primary use case is GRUB and other intermediate loaders, since it > would remove any need for these components to know any such details. > My aim is to make the next architecture that gets added to GRUB for > EFI boot 100% generic. Understood, thanks. It sounds plausible to me. Laszlo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel