[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <055622fb-93b9-49a3-804e-c2525edea4a2@intel.com>
Date: Tue, 20 Aug 2024 21:38:37 +0300
From: Adrian Hunter <adrian.hunter@...el.com>
To: Kai Huang <kai.huang@...el.com>, dave.hansen@...el.com,
kirill.shutemov@...ux.intel.com, bp@...en8.de, tglx@...utronix.de,
peterz@...radead.org, mingo@...hat.com, hpa@...or.com, seanjc@...gle.com,
pbonzini@...hat.com, dan.j.williams@...el.com
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
rick.p.edgecombe@...el.com, isaku.yamahata@...el.com, chao.gao@...el.com,
binbin.wu@...ux.intel.com
Subject: Re: [PATCH v2 09/10] x86/virt/tdx: Reduce TDMR's reserved areas by
using CMRs to find memory holes
> diff --git a/arch/x86/virt/vmx/tdx/tdx.h b/arch/x86/virt/vmx/tdx/tdx.h
> index 861ddf2c2e88..4b43eb774ffa 100644
> --- a/arch/x86/virt/vmx/tdx/tdx.h
> +++ b/arch/x86/virt/vmx/tdx/tdx.h
> @@ -40,6 +40,10 @@
> #define MD_FIELD_ID_UPDATE_VERSION 0x0800000100000005ULL
> #define MD_FIELD_ID_INTERNAL_VERSION 0x0800000100000006ULL
>
> +#define MD_FIELD_ID_NUM_CMRS 0x9000000100000000ULL
> +#define MD_FIELD_ID_CMR_BASE0 0x9000000300000080ULL
> +#define MD_FIELD_ID_CMR_SIZE0 0x9000000300000100ULL
For scripted checking against "global_metadata.json" it might be better
to stick to the same field names e.g.
MD_FIELD_ID_CMR_BASE0 -> MD_FIELD_ID_CMR_BASE
Powered by blists - more mailing lists