On Thu, Oct 17, 2024 at 03:11:10PM -0400, Peter Xu wrote: > On Thu, Oct 17, 2024 at 02:10:10PM -0300, Jason Gunthorpe wrote: > > > If so, maybe that's a non-issue for non-CoCo, where the VM object / > > > gmemfd object (when created) can have a flag marking that it's > > > always shared and can never be converted to private for any page > > > within. > > > > What is non-CoCo? Does it include the private/shared concept? > > I used that to represent the possible gmemfd use cases outside confidential > computing. > > So the private/shared things should still be around as fundamental property > of gmemfd, but it should be always shared and no convertion needed for the > whole lifecycle of the gmemfd when marked !CoCo.
But what does private mean in this context? Is it just like a bit of additional hypervisor security that the page is not mapped anyplace except the KVM stage 2 and the hypervisor can cause it to become mapped/shared at any time? But the guest has no idea about this? Jason
