[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0efe8492-e0da-4d97-8a6c-9cfe718f2d63@intel.com>
Date: Thu, 5 Dec 2024 10:10:10 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Kai Huang <kai.huang@...el.com>, kirill.shutemov@...ux.intel.com,
tglx@...utronix.de, bp@...en8.de, peterz@...radead.org, mingo@...hat.com,
hpa@...or.com, dan.j.williams@...el.com, seanjc@...gle.com,
pbonzini@...hat.com
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, rick.p.edgecombe@...el.com,
isaku.yamahata@...el.com, adrian.hunter@...el.com, nik.borisov@...e.com
Subject: Re: [PATCH v8 8.1/9] x86/virt/tdx: Reduce TDMR's reserved areas by
using CMRs to find memory holes
On 12/5/24 04:40, Kai Huang wrote:
> A TDX module initialization failure was reported on a Emerald Rapids
> platform [*]:
>
> virt/tdx: initialization failed: TDMR [0x0, 0x80000000): reserved areas exhausted.
> virt/tdx: module initialization failed (-28)
There's a *LOT* of changelog here, but I'm not sure how much of it is
actually relevant to the problem at hand. I also think it's wrong to to
present the problem as one of being too fine-grained.
Could you please rework the changelog and the comments to make this more
succinct?
Powered by blists - more mailing lists