[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65a500bda8dc89968f1308ea10f952312f955683.camel@intel.com>
Date: Fri, 3 Jan 2025 18:26:46 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "pbonzini@...hat.com"
<pbonzini@...hat.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
CC: "Zhao, Yan Y" <yan.y.zhao@...el.com>, "Huang, Kai" <kai.huang@...el.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH 12/13] x86/virt/tdx: Read essential global metadata for
KVM
On Wed, 2025-01-01 at 02:49 -0500, Paolo Bonzini wrote:
> Link: https://lore.kernel.org/kvm/0853b155ec9aac09c594caa60914ed6ea4dc0a71.camel@intel.com/ [1]
> Link: https://cdrdv2.intel.com/v1/dl/getContent/795381 [2]
> Signed-off-by: Kai Huang <kai.huang@...el.com>
> Signed-off-by: Rick Edgecombe <rick.p.edgecombe@...el.com>
> Message-ID: <20241030190039.77971-4-rick.p.edgecombe@...el.com>
It looks like this has the code changes from:
https://lore.kernel.org/kvm/20241221010704.14155-1-kai.huang@intel.com/
but not the log updates. The main missing piece is the explanation of why to go
with 128 size over the documented 32 and to check the size at runtime. I think
the history is good to record in the log.
Powered by blists - more mailing lists