From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mx.groups.io with SMTP id smtpd.web10.18063.1686835048653451197 for ; Thu, 15 Jun 2023 06:17:29 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@canonical.com header.s=20210705 header.b=Xt4oMsVc; spf=pass (domain: canonical.com, ip: 185.125.188.123, mailfrom: heinrich.schuchardt@canonical.com) Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 897BD3F120 for ; Thu, 15 Jun 2023 13:17:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1686835046; bh=AfJ/4u4Ccr29ovN7EZH9UsphGsgm7QFRLXJ5glGY/AQ=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Xt4oMsVcmFUo9q4qVqJl3qR5SxuHqA+S/dAaSpvS8jFyUrCnq4UcFe/rkjDYZrRKJ rDzJ0OikzJn6mbX5uSHGLq68JC06kbMHcACZ2S+agxg15PlWJPBLtgI3cP39HXAq+4 8ha7Rrx/oluwM9IWidHefKob3zw7JFvYp2B9CRgfCgu1D01DR2enpHq/zqW6phSlC6 uKYqPiukmet27l0jJNq5yngwXMByD7IWwY6/XHiDqy9dtJw/j0RJoDE2uRUHhBWQ+4 m1w6OxEbUES7Ra7PLoImgt0msRJeid0BiNLvkiep3ytnBG0Yczr/KRd/99GtuezsLW Y9s8d//e0AErA== Received: by mail-wr1-f71.google.com with SMTP id ffacd0b85a97d-30fd136ccb7so1218759f8f.3 for ; Thu, 15 Jun 2023 06:17:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686835046; x=1689427046; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AfJ/4u4Ccr29ovN7EZH9UsphGsgm7QFRLXJ5glGY/AQ=; b=OKmfs/XxWCQd3+ANpeeJkdobme3qmawuwngdG8Zqt2f5p01sEBsXsMSsOKzeioHto1 K2avfQNrPrxTvV9sA2NzRq5SERDbck1DVovAOwM1dPTOgNJeVhXKmlP+PiqwOSznMvJ0 SfJmsXzSknTS1yS0QxWuZwW226TqHHCWWSQrT5d/H4kv0n+29CLBMuxbddM1gG42+vWT 3cE+u8mTFLTUvAuFGWFZMuDWxMiXVsx5c8pZXW4Sr/A+YYjs3lfd4w9iVXzVdhwLPqPt YWzFs46zvYJcMxIz9jHDfow1M3GnDdAH8WH7ixQ8ivPqNPALsXoECmUKeZC05JJpO+00 TMjA== X-Gm-Message-State: AC+VfDzljKr2zMNYoqL0pnXIVMPrGCYwi5yfcZbgROF+SVowKmkHfgPJ i9LYdSRboAzdgIOGRPE5/qVUF9kj2algOKZ29Fh96tnDBr4NfEdIvk6/sfIzVLxpb1r8KXxakp9 faao332miPNTQ9hoZ9o47XaLZQHDKjCY= X-Received: by 2002:adf:ee86:0:b0:2d1:3eb9:c3c2 with SMTP id b6-20020adfee86000000b002d13eb9c3c2mr10771533wro.54.1686835046228; Thu, 15 Jun 2023 06:17:26 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6hs9XTSJBFGXcbzOWUnhFaq2Iptl3P1Do/FBXOKsjU+/GzcWCUqqxkwAoRV+RitjZCibEpQA== X-Received: by 2002:adf:ee86:0:b0:2d1:3eb9:c3c2 with SMTP id b6-20020adfee86000000b002d13eb9c3c2mr10771514wro.54.1686835045767; Thu, 15 Jun 2023 06:17:25 -0700 (PDT) Received: from [192.168.123.67] (ip-084-119-033-219.um24.pools.vodafone-ip.de. [84.119.33.219]) by smtp.gmail.com with ESMTPSA id m9-20020adfe0c9000000b0030af15d7e41sm21213164wri.4.2023.06.15.06.17.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Jun 2023 06:17:25 -0700 (PDT) Message-ID: Date: Thu, 15 Jun 2023 15:17:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH 0/4] OvmfPkg/RiscVVirt: Separate code and variable storage To: Sunil V L Cc: devel@edk2.groups.io, Ard Biesheuvel , Jiewen Yao , Jordan Justen , Gerd Hoffmann , Andrei Warkentin , Dann Frazier References: <20230614170151.1204982-1-sunilvl@ventanamicro.com> From: Heinrich Schuchardt In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 6/15/23 13:50, Sunil V L wrote: > 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 same EDK II binary on old and new QEMU >> releases? >> > Hi Heinrich, > > While both unified and separate images can not be generated at the same > time, a build flag can be used by which the user can build one of > the schemes matching qemu capabilities. Default will be separate > code and vars matching the latest qemu. > > I believe this will alleviate the concern. If this looks better, let me > test and send v2. > > Thanks! > Sunil At least Debian and Ubuntu packaging relies on the separation of code and variables. So anyway we would not be able back-port EDK II as package to anything that does not have the upcoming QEMU release. It would be helpful to document the constraints in the yet to be created OvmfPkg/RiscVVirt/ReadMe.rst. Best regards Heinrich