Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp3846200pxp; Wed, 23 Mar 2022 06:55:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJziElRr82Nw+HZrVjDjryydLpiwLmLj9HYzYXR2tFBGAfNRelwcBc7vJSGUtWEyq2+Y1XEW X-Received: by 2002:a17:906:3acd:b0:6df:f6da:fbbb with SMTP id z13-20020a1709063acd00b006dff6dafbbbmr25432ejd.189.1648043720423; Wed, 23 Mar 2022 06:55:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648043720; cv=none; d=google.com; s=arc-20160816; b=NoqGoTm0KGIjc4UIW5sUBFpG/Wus70QH52bqWJ+Jr+ksFFSpxZ5PWt4bzYfXT0ozw2 kxdLNK+fo6lW585Y/GlcTh+s1vinKEsHdPtUzjQeUF8DhPE1BA7dvYgKfSwjPO+ERqcQ xl9dcpVKXpBy/9owG650uQRWgUFyqt6mOetlvIZxWu1D6VUNVlLxoi2wVn4VyCSHpD2M VhKyrP124Zx52LBQEUjwxbPcNMk0k6M4en3hScJMQLhLK0QEMonwE0swQL9ck8njj6u5 bEFTgjNDyJVuOrb3aBYi76ZGSpxaliWp1AcNuSVlrfQ92FDRcLrXkamuKP0O0Xf1Uoip 98kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:to:from:cc:in-reply-to:subject:date:dkim-signature; bh=1tdwMzgNU3+9ty6xkH9fMGGweeCwRgg1Dr+d/9eH3Qc=; b=FqhJfdrYkANwtnk8wJ3LkuuvYOISTpl7UIr/gLHzhx5qywb7TxtCm/ujeWqpTIauDr wSK+yulw9tTGk9ysCXQbUOZhyb05tuWUNwmimCsWM2xVzue/8oGUTdiDGyEYhMHzQXC/ EX4nW5VtPP0yHyYFMP1vQA+A/6srmsIO/yjIoL5Zj7TbU0BLRRt8r905XWFQATMbNiI/ QUmIYZvj2+oUOPWt9o9I05fmTJX3Z0lpCQKrh2HPW9Zb6nv++GlyTgLPBnFsald20DuQ FfSptkh0LrI1mD4Bpky7vBVkg+7x3q5nuSy53B33pWyJs/94FdS1f1ywv7OP7WuJcbdF IcGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=Gb0kqmLT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v3-20020a50a443000000b00418c2b5bd90si15867558edb.114.2022.03.23.06.54.53; Wed, 23 Mar 2022 06:55:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=Gb0kqmLT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231133AbiCWBdz (ORCPT + 99 others); Tue, 22 Mar 2022 21:33:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58334 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230144AbiCWBdv (ORCPT ); Tue, 22 Mar 2022 21:33:51 -0400 Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8137933E1C for ; Tue, 22 Mar 2022 18:32:23 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id n7-20020a17090aab8700b001c6aa871860so323783pjq.2 for ; Tue, 22 Mar 2022 18:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20210112.gappssmtp.com; s=20210112; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=1tdwMzgNU3+9ty6xkH9fMGGweeCwRgg1Dr+d/9eH3Qc=; b=Gb0kqmLT129jUYWppYcf+O0ptJfQ1chsmf0FWqDF33rRzHXnu9VU00lf82mCBhvMOT xEjT2gr2VnGPjBV+knw3swrECBoiOXP+IaNN3IZCyRh3fJbtolZLh24hhLZODv+yUM2N GFIiTiqXmm3LkBcYok5oDYtJXWYgk85zciH63XgxqfYUs5VWqb539wKbEnisMMJ9+fHX 0fpcq6O1OMroRA0Ug9+nYbNeuaQKWOsm5Ke7a379DYXWXP67n6eeVB/IwCE/MNv+nWaK XUQCZ/XpQoF/T20F+m22W61xy9jzoFz/4ky/GkBcnOn9Lcp1py6ktikn1QFU79g7Rza4 I0qA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:subject:in-reply-to:cc:from:to:message-id :mime-version:content-transfer-encoding; bh=1tdwMzgNU3+9ty6xkH9fMGGweeCwRgg1Dr+d/9eH3Qc=; b=5Iud4obIyV5XrUK6XVT1YP30FkAPVC7oeSDLsbN9rkeTxqfIb/v3LW2EkvdaUE1d/Q 3mpyNdCG/Vq9j2pFpvG33hU1xy0SK+tQN5qzRYOJ7+Ekn+f1Y1tYThJbsRw9u72RPz9a 3u8uk4IkXZwtKuZmqAGijIuS6fjuEyLe4ecsXet1Lv5+t7nNGhivhhGJTpVMfQnJyJX4 V1ZlXEVancxfiDSKDWWSsYKbbP8NZ4SkOHgIqObR1gnZ6gRX/Fi29wg7c1YGll/mtWcm KQTplcryW0BpPdHOMl3hsthOJRqPSVCW+zKFo4pMFyb73d6WxR8F2wDxJ9ARuZqixsPZ GeWw== X-Gm-Message-State: AOAM532GfDXruS6TXZzUA1OngBxtnSV1LaMzLe5k3LLtZO/dmLI/VBQP cKCuS3+f0rxvOS9+YNUgd6n1zA== X-Received: by 2002:a17:903:32c9:b0:154:3a2d:fa89 with SMTP id i9-20020a17090332c900b001543a2dfa89mr17771357plr.3.1647999142958; Tue, 22 Mar 2022 18:32:22 -0700 (PDT) Received: from localhost ([12.3.194.138]) by smtp.gmail.com with ESMTPSA id l10-20020a056a00140a00b004c55d0dcbd1sm24433562pfu.120.2022.03.22.18.32.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Mar 2022 18:32:22 -0700 (PDT) Date: Tue, 22 Mar 2022 18:32:22 -0700 (PDT) X-Google-Original-Date: Tue, 22 Mar 2022 18:32:18 PDT (-0700) Subject: Re: [RFC PATCH V2 0/1] RISCV_EFI_BOOT_PROTOCOL support in linux In-Reply-To: <20220303145944.307321-1-sunilvl@ventanamicro.com> CC: ardb@kernel.org, Paul Walmsley , aou@eecs.berkeley.edu, heinrich.schuchardt@canonical.com, Atish Patra , apatel@ventanamicro.com, abner.chang@hpe.com, jrtc27@jrtc27.com, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, sunilvl@ventanamicro.com From: Palmer Dabbelt To: sunilvl@ventanamicro.com Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 03 Mar 2022 06:59:43 PST (-0800), sunilvl@ventanamicro.com wrote: > This patch adds support for getting the boot hart ID using new > RISCV_EFI_BOOT_PROTOCOL in linux efi stub. While there is an existing > solution of passing the boot hart ID through Device Tree, it doesn't work > for ACPI. Hence an EFI protocol protocol is recommended which works for > both DT and ACPI based platforms. > > The latest draft spec of this new protocol is available at > https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc2/RISCV_UEFI_PROTOCOL-spec.pdf This looks fine to me, but we need the spec folk to commit to this being a stable interface before we can start using it. Historically that's been "frozen" for RISC-V specs, but I'm not sure how that all fits together in EFI land as IIUC we also have to follow the UEFI forum's process. Last I checked you guys understood that better than I did, so Acked-by: Palmer Dabbelt # pending spec freeze I had a minor comment about the error message, as well. Thanks! > This linux ptach can be found in: > riscv_boot_protocol_rfc_v2 branch at > https://github.com/vlsunil/linux.git > > This is tested in qemu with u-boot 2022.04.rc3. > > Changes since V1: > - Rebased to get the "Fix get_boot_hartid_from_fdt() return value" > patch > - Removed mixed_mode member > - Separated return value and status. > > Sunil V L (1): > riscv/efi_stub: Add support for RISCV_EFI_BOOT_PROTOCOL > > drivers/firmware/efi/libstub/efistub.h | 7 ++++++ > drivers/firmware/efi/libstub/riscv-stub.c | 29 +++++++++++++++++++---- > include/linux/efi.h | 1 + > 3 files changed, 32 insertions(+), 5 deletions(-)