On Thu, May 5, 2022 at 6:47 PM Kai Huang <kai.huang@xxxxxxxxx> wrote: > > On Thu, 2022-05-05 at 18:15 -0700, Dan Williams wrote: > > On Thu, May 5, 2022 at 5:46 PM Kai Huang <kai.huang@xxxxxxxxx> wrote: > > > > > > On Thu, 2022-05-05 at 17:22 -0700, Dan Williams wrote: > > > > On Thu, May 5, 2022 at 3:14 PM Kai Huang <kai.huang@xxxxxxxxx> wrote: > > > > > > > > > > Thanks for feedback! > > > > > > > > > > On Thu, 2022-05-05 at 06:51 -0700, Dan Williams wrote: > > > > > > [ add Mike ] > > > > > > > > > > > > > > > > > > On Thu, May 5, 2022 at 2:54 AM Kai Huang <kai.huang@xxxxxxxxx> wrote: > > > > > > [..] > > > > > > > > > > > > > > Hi Dave, > > > > > > > > > > > > > > Sorry to ping (trying to close this). > > > > > > > > > > > > > > Given we don't need to consider kmem-hot-add legacy PMEM after TDX module > > > > > > > initialization, I think for now it's totally fine to exclude legacy PMEMs from > > > > > > > TDMRs. The worst case is when someone tries to use them as TD guest backend > > > > > > > directly, the TD will fail to create. IMO it's acceptable, as it is supposedly > > > > > > > that no one should just use some random backend to run TD. > > > > > > > > > > > > The platform will already do this, right? > > > > > > > > > > > > > > > > In the current v3 implementation, we don't have any code to handle memory > > > > > hotplug, therefore nothing prevents people from adding legacy PMEMs as system > > > > > RAM using kmem driver. In order to guarantee all pages managed by page > > > > > > > > That's the fundamental question I am asking why is "guarantee all > > > > pages managed by page allocator are TDX memory". That seems overkill > > > > compared to indicating the incompatibility after the fact. > > > > > > As I explained, the reason is I don't want to modify page allocator to > > > distinguish TDX and non-TDX allocation, for instance, having to have a ZONE_TDX > > > and GFP_TDX. > > > > Right, TDX details do not belong at that level, but it will work > > almost all the time if you do nothing to "guarantee" all TDX capable > > pages all the time. > > "almost all the time" do you mean? > > > > > > KVM depends on host's page fault handler to allocate the page. In fact KVM only > > > consumes PFN from host's page tables. For now only RAM is TDX memory. By > > > guaranteeing all pages in page allocator is TDX memory, we can easily use > > > anonymous pages as TD guest memory. > > > > Again, TDX capable pages will be the overwhelming default, why are you > > worried about cluttering the memory hotplug path for nice corner > > cases. > > Firstly perhaps I forgot to mention there are two concepts about TDX memory, so > let me clarify first: > > 1) Convertible Memory Regions (CMRs). This is reported by BIOS (thus static) to > indicate which memory regions *can* be used as TDX memory. This basically means > all RAM during boot for now. > > 2) TD Memory Regions (TDMRs). Memory pages in CMRs are not automatically TDX > usable memory. The TDX module needs to be configured which (convertible) memory > regions can be used as TDX memory. Kernel is responsible for choosing the > ranges, and configure to the TDX module. If a convertible memory page is not > included into TDMRs, the TDX module will report error when it is assigned to a > TD. > > > > > Consider the fact that end users can break the kernel by specifying > > invalid memmap= command line options. The memory hotplug code does not > > take any steps to add safety in those cases because there are already > > too many ways it can go wrong. TDX is just one more corner case where > > the memmap= user needs to be careful. Otherwise, it is up to the > > platform firmware to make sure everything in the base memory map is > > TDX capable, and then all you need is documentation about the failure > > mode when extending "System RAM" beyond that baseline. > > So the fact is, if we don't include legacy PMEMs into TDMRs, and don't do > anything in memory hotplug, then if user does kmem-hot-add legacy PMEMs as > system RAM, a live TD may eventually be killed. > > If such case is a corner case that we don't need to guarantee, then even better. > And we have an additional reason that those legacy PMEMs don't need to be in > TDMRs. As you suggested, we can add some documentation to point out. > > But the point we want to do some code check and prevent memory hotplug is, as > Dave said, we want this piece of code to work on *ANY* TDX capable machines, > including future machines which may, i.e. supports NVDIMM/CLX memory as TDX > memory. If we don't do any code check in memory hotplug in this series, then > when this code runs in future platforms, user can plug NVDIMM or CLX memory as > system RAM thus break the assumption "all pages in page allocator are TDX > memory", which eventually leads to live TDs being killed potentially. > > Dave said we need to guarantee this code can work on *ANY* TDX machines. Some > documentation saying it only works one some platforms and you shouldn't do > things on other platforms are not good enough: > > https://lore.kernel.org/lkml/cover.1649219184.git.kai.huang@xxxxxxxxx/T/#m6df45b6e1702bb03dcb027044a0dabf30a86e471 Yes, the incompatible cases cannot be ignored, but I disagree that they actively need to be prevented. One way to achieve that is to explicitly enumerate TDX capable memory and document how mempolicy can be used to avoid killing TDs. > > > shmem to support a new fd-based backend which doesn't require having to mmap() > > > TD guest memory to host userspace: > > > > > > https://lore.kernel.org/kvm/20220310140911.50924-1-chao.p.peng@xxxxxxxxxxxxxxx/ > > > > > > Also, besides TD guest memory, there are some per-TD control data structures > > > (which must be TDX memory too) need to be allocated for each TD. Normal memory > > > allocation APIs can be used for such allocation if we guarantee all pages in > > > page allocator is TDX memory. > > > > You don't need that guarantee, just check it after the fact and fail > > if that assertion fails. It should almost always be the case that it > > succeeds and if it doesn't then something special is happening with > > that system and the end user has effectively opt-ed out of TDX > > operation. > > This doesn't guarantee consistent behaviour. For instance, for one TD it can be > created, while the second may fail. We should provide a consistent service. Yes, there needs to be enumeration and policy knobs to avoid failures, hard coded "no memory hotplug" hacks do not seem the right enumeration and policy knobs to me. > The thing is anyway we need to configure some memory regions to the TDX module. > To me there's no reason we don't want to guarantee all pages in page allocator > are TDX memory. > > > > > > > > allocator are all TDX memory, the v3 implementation needs to always include > > > > > legacy PMEMs as TDX memory so that even people truly add legacy PMEMs as system > > > > > RAM, we can still guarantee all pages in page allocator are TDX memory. > > > > > > > > Why? > > > > > > If we don't include legacy PMEMs as TDX memory, then after they are hot-added as > > > system RAM using kmem driver, the assumption of "all pages in page allocator are > > > TDX memory" is broken. A TD can be killed during runtime. > > > > Yes, that is what the end user asked for. If they don't want that to > > happen then the policy decision about using kmem needs to be updated > > in userspace, not hard code that policy decision towards TDX inside > > the kernel. > > This is also fine to me. But please also see above Dave's comment. Dave is right, the implementation can not just ignore the conflict. To me, enumeration plus error reporting allows for flexibility without hard coding policy in the kernel.
