From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id 0070BAC13EE for ; Thu, 7 Sep 2023 15:13:26 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=Z71zYqmw+x6HfaAyujCMTVUcKvwKbHj2PRzbcEOsoC4=; c=relaxed/simple; d=groups.io; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Language:Content-Type:Content-Transfer-Encoding; s=20140610; t=1694099605; v=1; b=Fzvw5r/Ywe9+YaGVnn+4WL6issQhfNaiRGnAyGQjq9WT0HAQ4BMZOpcgPykW3hUOSsCn3Wuv +xhkoklgQg3jQ8mAZvP7HGo2Ul65C3Q0NnQVYGj+J2gdOSNnBJ+OtCKH6VECCszas/sp6ish62E pETZykYcZyysJ2tN7sETyIdA= X-Received: by 127.0.0.2 with SMTP id hhhgYY7687511xtUlVpbMBM9; Thu, 07 Sep 2023 08:13:25 -0700 X-Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web11.15602.1694099605124057073 for ; Thu, 07 Sep 2023 08:13:25 -0700 X-Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-477-1s95aPkGPvag4G3DsJ_W8g-1; Thu, 07 Sep 2023 11:13:23 -0400 X-MC-Unique: 1s95aPkGPvag4G3DsJ_W8g-1 X-Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5BE2D3C11A10; Thu, 7 Sep 2023 15:13:22 +0000 (UTC) X-Received: from [10.39.195.82] (unknown [10.39.195.82]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 010FC63F6C; Thu, 7 Sep 2023 15:13:19 +0000 (UTC) Message-ID: <46ab5d53-d5e0-46dd-e906-4c950af69919@redhat.com> Date: Thu, 7 Sep 2023 17:13:18 +0200 MIME-Version: 1.0 Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/RiscVVirt/README.md: bring your own OpenSBI To: edk2-devel-groups-io Cc: Andrei Warkentin , Ard Biesheuvel , Gerd Hoffmann , Jiewen Yao , Jordan Justen , Sunil V L References: <20230907145825.87830-1-lersek@redhat.com> From: "Laszlo Ersek" In-Reply-To: <20230907145825.87830-1-lersek@redhat.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,lersek@redhat.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: PNnDXM1bzGDhrKUBTeTAOtbfx7686176AA= Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b="Fzvw5r/Y"; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=redhat.com (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io On 9/7/23 16:58, Laszlo Ersek wrote: > Explain how users can compose their pre-OS environment purely from > binaries they've built themselves. >=20 > Cc: Andrei Warkentin > Cc: Ard Biesheuvel > Cc: Gerd Hoffmann > Cc: Jiewen Yao > Cc: Jordan Justen > Cc: Sunil V L > Signed-off-by: Laszlo Ersek > --- >=20 > Notes: > rendered version: > =20 > https://github.com/lersek/edk2/tree/bring-your-own-opensbi/OvmfPkg/Ri= scVVirt#test-with-your-own-opensbi-binary >=20 > OvmfPkg/RiscVVirt/README.md | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) >=20 > diff --git a/OvmfPkg/RiscVVirt/README.md b/OvmfPkg/RiscVVirt/README.md > index 8c3ac37b802a..dbb40bbe89b0 100644 > --- a/OvmfPkg/RiscVVirt/README.md > +++ b/OvmfPkg/RiscVVirt/README.md > @@ -69,3 +69,20 @@ Below example shows how to boot openSUSE Tumbleweed E2= 0. > -device virtio-net-pci,netdev=3Dnet0 \ > -device virtio-blk-device,drive=3Dhd0 \ > -drive file=3DopenSUSE-Tumbleweed-RISC-V-E20-efi.riscv64.raw,for= mat=3Draw,id=3Dhd0 > + > +## Test with your own OpenSBI binary > +Using the above QEMU command line, **RISCV_VIRT_CODE.fd** is launched by= the > +OpenSBI binary that is bundled with QEMU. You can build your own OpenSBI= binary > +as well: > + > + OPENSBI_DIR=3D... > + git clone https://github.com/riscv/opensbi.git $OPENSBI_DIR > + make -C $OPENSBI_DIR \ > + -j $(getconf _NPROCESSORS_ONLN) \ > + CROSS_COMPILE=3Driscv64-linux-gnu- \ > + PLATFORM=3Dgeneric > + > +then specify that binary for QEMU, with the following additional command= line > +option: > + > + -bios $OPENSBI_DIR/build/platform/generic/firmware/fw_dynamic.bin Further tweaks on the horizon (for v2, or on top), highlighted by Drew Jones: - explain -kernel/-initrd/-append (after testing it, of course! I'm unsure if fw_cfg kernel boot actually works with RiscVVirt!) - point out that -bios (OpenSBI) makes no difference under KVM, as KVM services those SBI ecalls - explain "acpi=3Doff" (in the context, not in the added text): Linux support (i.e. the ACPI *consumer* side) is still under development / work in progress. Laszlo -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#108400): https://edk2.groups.io/g/devel/message/108400 Mute This Topic: https://groups.io/mt/101216052/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/19134562= 12/xyzzy [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-