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 AD8CDD811D0 for ; Thu, 1 Feb 2024 08:35:29 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=HpfsSTK7v+5TwLlpwi4spQhxoHtYU1nHHaigiDKmh7I=; c=relaxed/simple; d=groups.io; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Disposition; s=20140610; t=1706776528; v=1; b=qnVuZnL7l/Sy9WSg/pOu9TNCyTUbDiGYtErSrGelNW6qCVhHKKi0tta2MhW+g8v9toChgXw6 ILSK5m2keqpJoxQB7e+vR/UeGNxz25YODXi+ELsVUfTIGv2DLicAToT2eh+XE3mWZFO7FeN89jZ PWW1XLqAb5oXn/tGqZAA0cLc= X-Received: by 127.0.0.2 with SMTP id RahVYY7687511xy4bcGUQ6Vb; Thu, 01 Feb 2024 00:35:28 -0800 X-Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web10.11266.1706776527592277988 for ; Thu, 01 Feb 2024 00:35:27 -0800 X-Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-96-gt-l4FonMce9jZryL43aXQ-1; Thu, 01 Feb 2024 03:35:21 -0500 X-MC-Unique: gt-l4FonMce9jZryL43aXQ-1 X-Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id E33E1185A782; Thu, 1 Feb 2024 08:35:20 +0000 (UTC) X-Received: from sirius.home.kraxel.org (unknown [10.39.193.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 35A61492BC8; Thu, 1 Feb 2024 08:35:20 +0000 (UTC) X-Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 056FB1800908; Thu, 1 Feb 2024 09:35:14 +0100 (CET) Date: Thu, 1 Feb 2024 09:35:14 +0100 From: "Gerd Hoffmann" To: Tom Lendacky Cc: devel@edk2.groups.io, Ard Biesheuvel , Erdem Aktas , Jiewen Yao , Laszlo Ersek , Liming Gao , Michael D Kinney , Min Xu , Zhiguang Liu , Rahul Kumar , Ray Ni , Michael Roth Subject: Re: [edk2-devel] [PATCH 03/16] MdePkg/BaseLib: Add a new VMGEXIT instruction invocation for SVSM Message-ID: References: <38bd6d829d25b89d416fa0f40eb5cc4487a0290f.1706307195.git.thomas.lendacky@amd.com> <34a1d889-a5b3-4cb0-8e8f-cabed9d14f2f@amd.com> <6rdteovxthwvxqvr2aey2yqci7zzkle3qty423jm7ysejxvapf@2dk3dp4ftsmn> <2deccf7e-6ff9-4362-8bb8-5de2239cc653@amd.com> MIME-Version: 1.0 In-Reply-To: <2deccf7e-6ff9-4362-8bb8-5de2239cc653@amd.com> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 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,kraxel@redhat.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: DF3cRjEvUBeNnn4WMhd85xtbx7686176AA= Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=qnVuZnL7; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=redhat.com (policy=none) On Wed, Jan 31, 2024 at 12:30:35PM -0600, Tom Lendacky wrote: > On 1/30/24 05:51, Gerd Hoffmann wrote: > > > > See also patch #13 sub-thread. Maybe just move the 32-bit build to the > > Null versions of the Libraries. > > > > SEV-SNP + SVSM apparently is 64-bit only already (there is no 32-bit > > calling convention). > > > > Over the last year Intel landed full 64-bit PEI support in edk2, which > > means the pure 64-bit build (OvmfPkgX64.dsc) has feature parity with > > the 32-bit PEI / 64-bit DXE build (OvmfPkgIa32X64.dsc). > > > > So maybe we can simply leave 32-bit support behind and remove SEV > > support from OvmfPkgIa32X64.dsc and OvmfPkgIa32.dsc builds ... > > That would break anyone that is currently using OvmfPkgIa32X64.dsc for base > SEV (not ES or SNP), but I'm not sure if that is a real concern. For > OvmfPkgIa32.dsc, no version of SEV will work, so that is doable. > > Can we look at doing that cleanup after this series? I thought maybe removing 32-bit support first is easier, because you don't have to add 32-bit dummy code then. I'd leave that do you do decide though, doing the 32-bit cleanup as separate series is fine with me too. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#114937): https://edk2.groups.io/g/devel/message/114937 Mute This Topic: https://groups.io/mt/103986440/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-