[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <674fb35ae5108_3e0fe29466@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Tue, 3 Dec 2024 17:41:46 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Dan Williams <dan.j.williams@...el.com>, Thomas Gleixner
<tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov
<bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>, "Kirill A .
Shutemov" <kirill.shutemov@...ux.intel.com>
CC: <x86@...nel.org>, <linux-coco@...ts.linux.dev>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, Huang Ying <ying.huang@...el.com>, "Dan
Williams" <dan.j.williams@...el.com>, Kai Huang <kai.huang@...el.com>, "David
Hildenbrand" <david@...hat.com>, Oscar Salvador <osalvador@...e.de>, "H.
Peter Anvin" <hpa@...or.com>, Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH -V3 RESEND] x86, tdx, memory hotplug: Check whole
hot-adding memory range for TDX
Dan Williams wrote:
> Drop my Reviewed-by as I now realize that my reading of the changelog
> for commit abe8dbab8f9f "x86/virt/tdx: Use all system memory when
> initializing TDX module as TDX memory", and the presence of the
> "is_tdx_memory()" helper lead me astray. If the changelog had said "This
> approach requires *but does not validate* all memblock memory
> regions...", I might have been spared.
>
> Until the new "convertible memory ranges" (CMR) enabling [1] is settled the
> kernel just takes on faith that anything memblock thinks is memory is
> TDX compatible.
Missed a link:
https://lore.kernel.org/b152bd39f9b235d5b20b8579a058a7f2bdbc111d.1730118186.git.kai.huang@intel.com
Powered by blists - more mailing lists