From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136])
 by mx.groups.io with SMTP id smtpd.web11.96595.1673634857409055955
 for <devel@edk2.groups.io>;
 Fri, 13 Jan 2023 10:34:17 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="unable to parse pub key" header.i=@intel.com header.s=intel header.b=Wxvg1geQ;
 spf=pass (domain: intel.com, ip: 192.55.52.136, 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=1673634857; x=1705170857;
  h=message-id:date:mime-version:subject:to:cc:references:
   from:in-reply-to:content-transfer-encoding;
  bh=maqyRiRH6DUHJDhbl1NaxdENYoPoSKC/KAaI5OgE8oE=;
  b=Wxvg1geQyYAEPg5gCMbcdBKigJSHwv5/k1JlIOy5pGgctBx6jnbzvBq+
   VV3WjyUajpm0t3BkgFYtVgnJTete/z3Qptp8w8V+7E5hniI2dvGvCVknX
   hRSUaewdCPAW+cwkPdID+0zPuMPyuwLkQZ19jFDkq8Yeye8M9UPabA/uT
   rhwD9e5EW8h6qy9rT3hU57GuaSyzd7TbOBSs4lGCu/lZ5OGC6pQ6er7Ku
   t5cL3pUe3yCOzYopCcGL0Nd6PDMCKCVil5edI4R7SONl8XAXkglhCVbUX
   +7gB+LCI2H44VN1JHxvsdmoIDdJHitm4Isyw/Z6iVH+gF4bKwYA2+Vry5
   g==;
X-IronPort-AV: E=McAfee;i="6500,9779,10589"; a="303761475"
X-IronPort-AV: E=Sophos;i="5.97,214,1669104000"; 
   d="scan'208";a="303761475"
Received: from orsmga005.jf.intel.com ([10.7.209.41])
  by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jan 2023 10:34:17 -0800
X-IronPort-AV: E=McAfee;i="6500,9779,10589"; a="832155803"
X-IronPort-AV: E=Sophos;i="5.97,214,1669104000"; 
   d="scan'208";a="832155803"
Received: from cnjohnso-mobl1.amr.corp.intel.com (HELO [10.209.49.126]) ([10.209.49.126])
  by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jan 2023 10:34:16 -0800
Message-ID: <d2ff3032-5fa6-7d3e-67f0-ce0d7a9a7fdd@intel.com>
Date: Fri, 13 Jan 2023 10:34:15 -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: devel@edk2.groups.io, dionnaglaze@google.com
Cc: 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>
From: Dave Hansen <dave.hansen@intel.com>
In-Reply-To: <CAAH4kHa1WU_6505fYyvp=06RGyPoh_-Do++7oib=T23hEgy9ug@mail.gmail.com>
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 1/13/23 10:23, Dionna Glaze via groups.io wrote:
>> However, *NONE* of this points me in the direction of saying that we
>> should have an OS/firmware protocol to negotiate whether the firmware or
>> OS does page acceptance other than the existing UEFI memory map bit.
> We know of distributions that are going to release SEV-SNP support
> without unaccepted memory support,

Well, I guess that's a bit of a different problem.

I'd love to hear from the distros what they're planning on carrying
outside of mainline and what their plans are for the kernel side of this
series.