From: Dan Williams <dan.j.williams@intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Cc: <x86@kernel.org>, <linux-coco@lists.linux.dev>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Huang Ying <ying.huang@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>,
Kai Huang <kai.huang@intel.com>,
"David Hildenbrand" <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH -V3 RESEND] x86, tdx, memory hotplug: Check whole hot-adding memory range for TDX
Date: Tue, 3 Dec 2024 17:41:46 -0800 [thread overview]
Message-ID: <674fb35ae5108_3e0fe29466@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <674fb148d58aa_3e0fe294ce@dwillia2-mobl3.amr.corp.intel.com.notmuch>
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
prev parent reply other threads:[~2024-12-04 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 8:51 Huang Ying
2024-11-05 18:34 ` Dave Hansen
2024-11-06 8:09 ` Huang, Ying
2024-12-04 1:32 ` Dan Williams
2024-12-04 1:41 ` Dan Williams [this message]
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-all 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=674fb35ae5108_3e0fe29466@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
/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