public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Ni, Ray" <ray.ni@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	 "Xu, Min M" <min.m.xu@intel.com>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>,
	 Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
Date: Fri, 31 Mar 2023 11:26:06 +0200	[thread overview]
Message-ID: <dckxvjsu6dcfgz36zrdh4lvsxwmtupxi4cr3fupikq2eqqglm2@4oiucgtoz5n6> (raw)
In-Reply-To: <MN6PR11MB82443805DEBA9F26D3DDBE108C8F9@MN6PR11MB8244.namprd11.prod.outlook.com>

On Fri, Mar 31, 2023 at 08:02:00AM +0000, Ni, Ray wrote:
> Gerd,
> Can you give a Reviewed-by/Acked-by for the patch series?

> > This Bugzilla captures the same idea:
> > https://bugzilla.tianocore.org/show_bug.cgi?id=3394

Oh, the bug lists even more places which care about
the physical address width.

Sure you want merge the series in this apparently
incomplete state?

It should have no bad effects on OVMF though, so if you
prefer to merge this as-is and implement the suggested
library solution as separate patch series:

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

take care,
  Gerd


  reply	other threads:[~2023-03-31  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174E9488256AAAA5.22739@groups.io>
2023-03-28 14:10 ` [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA Ni, Ray
2023-03-28 14:13 ` Ni, Ray
     [not found] ` <17509A92F1FF60E5.28404@groups.io>
2023-03-30  2:26   ` Ni, Ray
2023-03-30  7:25     ` Gerd Hoffmann
2023-03-30  8:41       ` Ni, Ray
2023-03-30  9:03         ` Gerd Hoffmann
2023-03-31  7:24           ` Ni, Ray
     [not found]           ` <17517033A2B187E0.12651@groups.io>
2023-03-31  8:02             ` Ni, Ray
2023-03-31  9:26               ` Gerd Hoffmann [this message]
2023-03-30 15:28     ` Lendacky, Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dckxvjsu6dcfgz36zrdh4lvsxwmtupxi4cr3fupikq2eqqglm2@4oiucgtoz5n6 \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox