From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115])
 by mx.groups.io with SMTP id smtpd.web11.30963.1674600393088620811
 for <devel@edk2.groups.io>;
 Tue, 24 Jan 2023 14:46:33 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="unable to parse pub key" header.i=@intel.com header.s=intel header.b=T1XU2XEN;
 spf=pass (domain: intel.com, ip: 192.55.52.115, mailfrom: dave.hansen@intel.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
  d=intel.com; i=@intel.com; q=dns/txt; s=Intel;
  t=1674600393; x=1706136393;
  h=message-id:date:mime-version:subject:to:cc:references:
   from:in-reply-to:content-transfer-encoding;
  bh=VnJ/sPE99jRK8dY6h3JHaHLfAvoSLcl4OXkeAyHZP10=;
  b=T1XU2XENV8sPGcqLNjVnXezjdgkseKXEmJhpnrdHssIoKIspG88DPse8
   glaqSRyFICj4Dn8MhvevqoHyDd7xKT1JiyT9YuLtdGeMF4mGOdZlBqSAU
   c1ZnGYt96TIIIHuM9Y/k3jzh+ZGHCxb6dXhqEaPDenDwfxzu/VHo3wm6Y
   IiIf92W7kKy8s7hIItDeaguU21ti5ii7RGAVdrZvSZ1hYegfYFO+1D845
   oA1GT+FU5LafhM9BRb3QN0FZ8Az4bN3zDTBpr9yE0bv0bPmEDPpV9RSAI
   ush1wN5BPy4gUcJDyvbyOBxNLX5RlcLNat76xIJNcExDk5dZ8g7X68LPq
   g==;
X-IronPort-AV: E=McAfee;i="6500,9779,10600"; a="326463383"
X-IronPort-AV: E=Sophos;i="5.97,243,1669104000"; 
   d="scan'208";a="326463383"
Received: from fmsmga005.fm.intel.com ([10.253.24.32])
  by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jan 2023 14:46:32 -0800
X-IronPort-AV: E=McAfee;i="6500,9779,10600"; a="991053145"
X-IronPort-AV: E=Sophos;i="5.97,243,1669104000"; 
   d="scan'208";a="991053145"
Received: from hvanorma-mobl.amr.corp.intel.com (HELO [10.209.71.170]) ([10.209.71.170])
  by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jan 2023 14:46:32 -0800
Message-ID: <76983a6f-0407-155c-0986-dda41f0eddd9@intel.com>
Date: Tue, 24 Jan 2023 14:46:32 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: [edk2-devel] [PATCH v9 0/4] Add safe unaccepted memory behavior
To: Tom Lendacky <thomas.lendacky@amd.com>, devel@edk2.groups.io,
 kraxel@redhat.com
Cc: dionnaglaze@google.com, dave.hansen@linux.intel.com,
 Jiewen <jiewen.yao@intel.com>, "Shutemov, Kirill" <kirill.shutemov@intel.com>
References: <MW4PR11MB58725ED9D912BDC299E821538CC29@MW4PR11MB5872.namprd11.prod.outlook.com>
 <16581.1673625639418051810@groups.io>
 <CAAH4kHYgN1ZVevP7mDRT27bpjj+0tkyAVbtznzyfYVuryBU=2g@mail.gmail.com>
 <0918b9db-c949-75ce-a24e-f12f03865938@intel.com>
 <CAAH4kHa1WU_6505fYyvp=06RGyPoh_-Do++7oib=T23hEgy9ug@mail.gmail.com>
 <d2ff3032-5fa6-7d3e-67f0-ce0d7a9a7fdd@intel.com>
 <20230116102801.y3l6xn3gdgregn4k@sirius.home.kraxel.org>
 <d27b6d42-4753-2989-a5d3-bcc683efc1d3@amd.com>
From: Dave Hansen <dave.hansen@intel.com>
In-Reply-To: <d27b6d42-4753-2989-a5d3-bcc683efc1d3@amd.com>
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 1/24/23 14:42, Tom Lendacky wrote:
>> Fedora has near zero additional patches, so it pretty much depends on
>> how mainline merges stuff.  If SEV-SNP or TDX or both will land in an
>> upstream release before support for unaccepted memory lands too you'll
> 
> Sorry, just saw this...
> 
> SEV-SNP guest support has already landed upstream and is part of the
> 5.19 kernel. So without this interface, anyone using a newer OVMF with a
> 5.19 to whatever kernel just before unaccepted memory finally gets
> pulled into, would have issues.

Also, just to reiterate: my whinging about this has been purely
TDX-specific.  It's a bit of a shame that things happened in this order,
but SEV-SNP does seem to have a legitimate need here, separate from TDX.

I'll be quiet now. :)