From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qt1-f169.google.com (mail-qt1-f169.google.com [209.85.160.169]) by mx.groups.io with SMTP id smtpd.web11.11121.1686803168194962703 for ; Wed, 14 Jun 2023 21:26:08 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@ventanamicro.com header.s=google header.b=fZZUnYfy; spf=pass (domain: ventanamicro.com, ip: 209.85.160.169, mailfrom: sunilvl@ventanamicro.com) Received: by mail-qt1-f169.google.com with SMTP id d75a77b69052e-3f86a7f3a65so26211501cf.0 for ; Wed, 14 Jun 2023 21:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; t=1686803167; x=1689395167; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=vlcQQ7lSqyrgKeF5zhqvgl+JptONHMDmq612iSs7WWg=; b=fZZUnYfy3zaGAwJi1XWjDv22bJmAD8frZHVCa1VFL1N/blFOUKfgrcP6aNObEOu6NS dJqIUKY0j2q7Kmqstab7zGj0k8H3sT+plG/bTRmqA/tWPzxUNOFg+nprJ7wHiaZ+2zD7 hNj+i1NjMEdAT0LW2j3Q+YlUxgfbafvfLD07EBVGFdZllAhJzVpRnj+FEZUYI1WzYEMz mxedLNzm0jMwu4NVXOprvuqWp6ukLz1dwczFJKtQHQrm2IVsZzvK40I44DzYwsLI85Aj 1+fUgvPTZ8MVMDEVMVedOxmUV51CsmKvF9jOZ1YPt3tVSAtFOq8Vbq9q15i8EBJ7r2H3 Xw6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686803167; x=1689395167; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=vlcQQ7lSqyrgKeF5zhqvgl+JptONHMDmq612iSs7WWg=; b=lGkC544ENoexsPfvLWFpDD80DXev2Yt5izlWVP61gTe+Hu9COQDEa1u4Qqx0Thng18 9RXBowiM7977flaNQUaCE34pFI7Zmpcyuce9b3iiyi6oaxdr0spnVeltAEcxyOpEi9V5 5k6HnNBbMNhIFp1ug8kB68bQlDSzmTEhH8pEmZS6eu1kkWxSS+YLoolxwEmLyJsCyWZ2 PBuq1sA7GZd4/Kb9rgajGFPlFpObhse8dahq+8TAR4vwql3jgKjs+ounRLsfPNusitKY NUl2dTiRE6zenWFJpJ9AuFrnG7ezZZuKAtTe7EE6bChZ5aKrmIi37LN8DneLcSaERGst Lc6w== X-Gm-Message-State: AC+VfDx1QxtgneeHr6nEO544Ju761cW1bqyMs8HU+w7obUIFtOCLbhwO zuHRapHYFeu5yN+xnOOdWLC7JA== X-Google-Smtp-Source: ACHHUZ4lmseHYhH6WNJGH47kcGMPCN8/kPbawpAk/H7/IvMaGoVOcTaExG1zswcLSURKjiNYfSM2QA== X-Received: by 2002:a05:622a:88:b0:3e3:8ed5:a47e with SMTP id o8-20020a05622a008800b003e38ed5a47emr4918898qtw.10.1686803167220; Wed, 14 Jun 2023 21:26:07 -0700 (PDT) Return-Path: Received: from sunil-laptop ([106.51.184.72]) by smtp.gmail.com with ESMTPSA id t2-20020a655542000000b005143448896csm10914993pgr.58.2023.06.14.21.26.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Jun 2023 21:26:06 -0700 (PDT) Date: Thu, 15 Jun 2023 09:56:00 +0530 From: "Sunil V L" To: Heinrich Schuchardt Cc: devel@edk2.groups.io, Ard Biesheuvel , Jiewen Yao , Jordan Justen , Gerd Hoffmann , Andrei Warkentin , Dann Frazier Subject: Re: [PATCH 0/4] OvmfPkg/RiscVVirt: Separate code and variable storage Message-ID: References: <20230614170151.1204982-1-sunilvl@ventanamicro.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jun 14, 2023 at 07:11:18PM +0200, Heinrich Schuchardt wrote: > Sunil V L schrieb am Mi., 14. Juni 2023, 19:01: > > > Recent updates to RISC-V qemu virt platform merged today (07/14), > > have enabled both pflash devices for the S-mode payload like EDK2. > > These updates also aligned the design similar to other architectures > > where pflash0 is for read-only code and pflash1 for variable store. > > Previously only pflash1 was available for S-mode use. > > > > Current EDK2 will not work with this latest qemu changes since it always > > assumed to boot from pflash1. So, separate the code and variable > > store and use pflash0 to keep the code. > > > > Not all users will have the newest QEMU provided by their Linx distro. Will > it be possible to boot the the same EDK II binary on old and new QEMU > releases? > Hi Heinrich, I was initially thinking to have support for both unified and separate images something similar to x86. However, it doesn't work for RISC-V since we need code in the beginning of the image. So, if we try to add both unified and separate image support, the PCD variables for NVRAM get different values during build and boot will fail for one of the image. I don't think it is worth of the effort to have two different infrastructure files for old and new qemu. We discussed this issue in qemu community and consensus was it is better in the long term to move to this design while in short term we will have this incompatibility. Since RISC-V EDK2 is relatively new, I think it is OK to request people with old qemu to use older EDK2 or current stable release. For next stable release, both qemu and edk2 will be compatible to each other. Thanks, Sunil