From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mx.groups.io with SMTP id smtpd.web10.16555.1684829739349404193 for ; Tue, 23 May 2023 01:15:39 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=W5Sc1qzj; spf=pass (domain: kernel.org, ip: 139.178.84.217, mailfrom: ardb@kernel.org) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A4BCC62607 for ; Tue, 23 May 2023 08:15:38 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1A051C4339B for ; Tue, 23 May 2023 08:15:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684829738; bh=hwiH+aOOMriIggtz9aC2s7gTAGkwehH/P7MxuFzsqlI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=W5Sc1qzj8zrBwX59sIQWHj/5x4hLZ43TfI5t4MFFLeEBnCNYsN/T9RcG/pKaYKWSX vsUzaFrcK9EQjkYSTWan0ZCVl25qcRdFfMCRSpqLEAPHbAm0oOlhSuQ05naJN0CAcu 0zPEAjJD4HXkdU+T2imOMMN42C86fXNk3/+Z7hn64yiR9UiEKiSyQk21Qiabvgzz9J X06svo0Bl2IYIWc2pOtW0kl7aCcEqJd3mYFv6YvmAWPwGdQf4AU+c3hvDt8Ljuf1ZD pJuf+tu/rd5u6FPvVh8vpOwNq7iYBdLdhir8+7JEUuzCSx9PxwvSbXG8aFHlGFA5Vy z26YXq7SBniQA== Received: by mail-lf1-f53.google.com with SMTP id 2adb3069b0e04-4f3edc05aa5so2771141e87.3 for ; Tue, 23 May 2023 01:15:37 -0700 (PDT) X-Gm-Message-State: AC+VfDwKTVRPNUmjyt0IsdaUf6kdZIZIzEN77GlXT5/zQ46Y3xYS3JXB hWSSCqnq9HlJyVhAflccVRwDZ9oenJEu1fYbP/I= X-Google-Smtp-Source: ACHHUZ6D1RMZBJ5na0jYrcpsNd2vbXDDKyJeSOwlVXpiMR8GsTdFVaxcUj35rKsSjR1EKQ0p7qL+TWUk34dAnkdK4/w= X-Received: by 2002:a2e:8093:0:b0:2af:2fb0:923c with SMTP id i19-20020a2e8093000000b002af2fb0923cmr3341851ljg.17.1684829736064; Tue, 23 May 2023 01:15:36 -0700 (PDT) MIME-Version: 1.0 References: <1718e8ad-6ba3-5da8-85c5-76e48c42110d@redhat.com> <2e04e9da-5b5a-9c00-76fe-c149538ddc80@redhat.com> In-Reply-To: From: "Ard Biesheuvel" Date: Tue, 23 May 2023 10:15:24 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: managing memory attributes in PEI To: Gerd Hoffmann Cc: Laszlo Ersek , "Ni, Ray" , edk2-devel-groups-io , "Yao, Jiewen" , Taylor Beebe , Oliver Smith-Denny Content-Type: text/plain; charset="UTF-8" On Tue, 23 May 2023 at 10:05, Gerd Hoffmann wrote: > > Hi, > > > >> Before we enabled SMM for OVMF, we had never really used IA32X64 OVMF -- > > >> SMM-less ACPI S3 resume had just worked fine with X64-only OVMF. IA32X64 > > >> only proved a great platform option to fall back to, when we realized > > >> that on X64 OVMF, ACPI S3 resume wouldn't just seamlessly extend to SMM. > > > > > > I don't quite understand. So, what's the conclusion of IA32X64 OVMF? Keep it? Remove it? > > > > As long as edk2 (core modules) will continue supporting IA32X64 firmware > > platforms, I think keeping OVMF IA32X64 is useful, minimally as a test > > bed for those core modules / PCDs / boot paths. > > Agree. > > I'll go switch downstream SMM-enabled builds from OvmfPkgIa32X64.dsc to > OvmfPkgX64.dsc ASAP, so for virtualization use cases OvmfPkgIa32X64.dsc > will not be needed any more. > > But it indeed makes sense to keep OvmfPkgIa32X64.dsc for testing and CI > purposes. So the question what the future of OvmfPkgIa32X64.dsc (and > OvmfPkgIa32.dsc) should be is is more a question of what the overall > edk2 plans for IA32 are. > Indeed. Let's make it very clear that it only remains as a validation target, so keeping it alive only makes sense if other supported IA32X64 based platforms still exist as well.