From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [edk2-staging/RiscV64QemuVirt PATCH V7 18/20] OvmfPkg/RiscVVirt: Add SEC module To: Sunil V L ,devel@edk2.groups.io From: dhaval@rivosinc.com X-Originating-Location: Bengaluru, Karnataka, IN (171.76.87.8) X-Originating-Platform: Linux Chrome 109 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sun, 29 Jan 2023 21:17:30 -0800 References: <20230128191807.2080547-19-sunilvl@ventanamicro.com> In-Reply-To: <20230128191807.2080547-19-sunilvl@ventanamicro.com> Message-ID: <1214.1675055850703338989@groups.io> Content-Type: multipart/alternative; boundary="Pj9M0gDBVqxi1sLTxAZl" --Pj9M0gDBVqxi1sLTxAZl Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable BuildCpuHob (56, 32); Can we find a better programmatic way of doing this? SATP register could be= on method, or PCD? Also would help if you can clarify how we arrive at thi= s value 56. --Pj9M0gDBVqxi1sLTxAZl Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable BuildCpuHob (56, 32);
Ca= n we find a better programmatic way of doing this? SATP register could be o= n method, or PCD? Also would help if you can clarify how we arrive at this = value 56. --Pj9M0gDBVqxi1sLTxAZl--