From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Ackerley Tng <ackerleytng@google.com>,
Lisa Wang <wyihan@google.com>,
Andrew Jones <ajones@ventanamicro.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Chao Gao <chao.gao@intel.com>,
Chenyi Qiang <chenyi.qiang@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Erdem Aktas <erdemaktas@google.com>,
Ira Weiny <ira.weiny@intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Kiryl Shutsemau <kas@kernel.org>,
linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
"Pratik R. Sampat" <pratikrajesh.sampat@amd.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Roger Wang <runanwang@google.com>,
Ryan Afranji <afranji@google.com>, Sagi Shahar <sagis@google.com>,
Sean Christopherson <seanjc@google.com>,
Shuah Khan <shuah@kernel.org>, Oliver Upton <oupton@kernel.org>
Cc: Jeremiah McReynolds <jmcrey@google.com>,
kvm@vger.kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v13 13/22] KVM: selftests: Set first memory region as shared if guest_memfd
Date: Wed, 24 Jun 2026 23:43:35 +0800 [thread overview]
Message-ID: <f8937d16-4aed-44d9-a058-beff56eac4ad@intel.com> (raw)
In-Reply-To: <CAEvNRgEBiivp9tOHZnFmWvF6ek-Ar-m2B+hb=-H0dgAcM2=z8Q@mail.gmail.com>
On 6/16/2026 7:46 AM, Ackerley Tng wrote:
> Lisa Wang <wyihan@google.com> writes:
>
>> Set the initial state of the first memory region as shared if it is
>> backed by guest_memfd, so that the KVM selftest framework functions can
>> populate mmap()-ed guest_memfd memory the same way memory from other
>> memory providers are populated.
>>
>> For CoCo VMs, pages that need to be private are explicitly set to
>> private before executing the VM.
>>
>>
>> [...snip...]
>>
>> @@ -495,14 +497,16 @@ struct kvm_vm *__vm_create(struct vm_shape shape, u32 nr_runnable_vcpus,
>> vm = ____vm_create(shape);
>>
>> /*
>> - * Force GUEST_MEMFD for the primary memory region if necessary, e.g.
>> - * for CoCo VMs that require GUEST_MEMFD backed private memory.
>> + * Force GUEST_MEMFD for the primary memory region if necessary, and
>> + * initialize it as shared so the selftest framework can populate it
>> + * exactly like other memory providers.
>> */
>> - flags = 0;
>> - if (is_guest_memfd_required(shape))
>> + if (is_guest_memfd_required(shape)) {
>> flags |= KVM_MEM_GUEST_MEMFD;
>> + gmem_flags |= GUEST_MEMFD_FLAG_INIT_SHARED;
>> + }
>>
>
> Just noticed this while hacking some SNP tests.
>
>> - vm_userspace_mem_region_add(vm, VM_MEM_SRC_ANONYMOUS, 0, 0, nr_pages, flags);
>> + vm_mem_add(vm, VM_MEM_SRC_ANONYMOUS, 0, 0, nr_pages, flags, -1, 0, gmem_flags);
>> for (i = 0; i < NR_MEM_REGIONS; i++)
>> vm->memslots[i] = 0;
>>
>>
>> --
>> 2.54.0.746.g67dd491aae-goog
>
> I think this patch should fully buy into in-place conversions, so we
> need to also set GUEST_MEMFD_FLAG_MMAP:
>
> @@ -483,6 +483,7 @@ struct kvm_vm *__vm_create(struct vm_shape shape,
> u32 nr_runnable_vcpus,
> {
> u64 nr_pages = vm_nr_pages_required(shape.mode, nr_runnable_vcpus,
> nr_extra_pages);
> + enum vm_mem_backing_src_type src_type = VM_MEM_SRC_ANONYMOUS;
> struct userspace_mem_region *slot0;
> u64 gmem_flags = 0;
> struct kvm_vm *vm;
> @@ -503,10 +504,16 @@ struct kvm_vm *__vm_create(struct vm_shape
> shape, u32 nr_runnable_vcpus,
> */
> if (is_guest_memfd_required(shape)) {
> flags |= KVM_MEM_GUEST_MEMFD;
> - gmem_flags |= GUEST_MEMFD_FLAG_INIT_SHARED;
> + gmem_flags |= GUEST_MEMFD_FLAG_INIT_SHARED | GUEST_MEMFD_FLAG_MMAP;
GUEST_MEMFD_FLAG_INIT_SHARED is valid only when the memory attributes is
per-gmem.
we need to check KVM_CAP_GUEST_MEMFD_FLAGS or kvm_has_gmem_attributes.
next prev parent reply other threads:[~2026-06-24 15:43 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 23:16 [PATCH v13 00/22] TDX KVM selftests Lisa Wang
2026-05-21 23:16 ` [PATCH v13 01/22] KVM: selftests: Add macros to simplify creating VM shapes for non-default types Lisa Wang
2026-06-16 8:57 ` Xiaoyao Li
2026-06-16 16:51 ` Sean Christopherson
2026-06-17 3:04 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 02/22] KVM: selftests: Update kvm_init_vm_address_properties() for TDX Lisa Wang
2026-06-17 2:37 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 03/22] KVM: selftests: Initialize the TDX VM Lisa Wang
2026-06-08 5:57 ` Binbin Wu
2026-06-15 23:33 ` Lisa Wang
2026-06-17 3:21 ` Xiaoyao Li
2026-06-24 23:50 ` Lisa Wang
2026-06-25 2:37 ` Xiaoyao Li
2026-06-17 3:54 ` Xiaoyao Li
2026-06-17 9:50 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 04/22] KVM: selftests: TDX: Use KVM_TDX_CAPABILITIES to validate TDs' attribute configuration Lisa Wang
2026-06-17 3:51 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 05/22] KVM: selftests: Expose segment definitions to assembly files Lisa Wang
2026-06-23 1:47 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 06/22] tools: include: Add kbuild.h for assembly structure offsets Lisa Wang
2026-06-08 6:12 ` Binbin Wu
2026-05-21 23:16 ` [PATCH v13 07/22] KVM: selftests: Introduce structures for TDX guest boot parameters Lisa Wang
2026-05-22 17:43 ` Yosry Ahmed
2026-05-22 23:05 ` Sean Christopherson
2026-05-22 23:50 ` Yosry Ahmed
2026-05-28 19:25 ` Yosry Ahmed
2026-05-21 23:16 ` [PATCH v13 08/22] KVM: selftests: Add TDX boot code Lisa Wang
2026-06-16 9:21 ` Chenyi Qiang
2026-06-23 1:59 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 09/22] KVM: selftests: Expose functions to get default sregs values Lisa Wang
2026-06-08 6:39 ` Binbin Wu
2026-06-15 10:54 ` Chenyi Qiang
2026-05-21 23:16 ` [PATCH v13 10/22] KVM: selftests: Set up TDX boot code region Lisa Wang
2026-05-21 23:16 ` [PATCH v13 11/22] KVM: selftests: Set up TDX boot parameters region Lisa Wang
2026-06-08 7:23 ` Binbin Wu
2026-06-24 16:07 ` Xiaoyao Li
2026-05-21 23:16 ` [PATCH v13 12/22] KVM: selftests: Back the first memory region with guest_memfd for TDX Lisa Wang
2026-06-08 7:31 ` Binbin Wu
2026-05-21 23:16 ` [PATCH v13 13/22] KVM: selftests: Set first memory region as shared if guest_memfd Lisa Wang
2026-06-08 8:03 ` Binbin Wu
2026-06-16 0:04 ` Lisa Wang
2026-06-15 23:46 ` Ackerley Tng
2026-06-24 15:43 ` Xiaoyao Li [this message]
2026-05-21 23:16 ` [PATCH v13 14/22] KVM: selftests: Expose function to allocate vCPU stack Lisa Wang
2026-05-21 23:16 ` [PATCH v13 15/22] KVM: selftests: Call KVM_TDX_INIT_VCPU when creating a new TDX vcpu Lisa Wang
2026-06-08 8:34 ` Binbin Wu
2026-05-21 23:16 ` [PATCH v13 16/22] KVM: selftests: Load per-vCPU guest stack in TDX boot parameters Lisa Wang
2026-06-09 5:37 ` Binbin Wu
2026-05-21 23:16 ` [PATCH v13 17/22] KVM: selftests: Set entry point for TDX guest code Lisa Wang
2026-05-21 23:16 ` [PATCH v13 18/22] KVM: selftests: Add helpers to init TDX memory and finalize VM Lisa Wang
2026-05-21 23:17 ` [PATCH v13 19/22] KVM: selftests: Finalize TD memory as part of kvm_arch_vm_finalize_vcpus Lisa Wang
2026-06-05 13:58 ` Ackerley Tng
2026-06-05 17:58 ` Sean Christopherson
2026-06-05 18:27 ` Ackerley Tng
2026-06-05 20:48 ` Sean Christopherson
2026-06-16 0:26 ` Ackerley Tng
2026-06-16 14:36 ` Sean Christopherson
2026-06-16 16:13 ` Ackerley Tng
2026-06-16 17:06 ` Sean Christopherson
2026-05-21 23:17 ` [PATCH v13 20/22] KVM: selftests: Implement MMIO WRITE for the TDX VM Lisa Wang
2026-06-09 6:45 ` Binbin Wu
2026-06-16 18:20 ` Sean Christopherson
2026-05-21 23:17 ` [PATCH v13 21/22] KVM: selftests: Add ucall support for TDX Lisa Wang
2026-06-16 18:47 ` Sean Christopherson
2026-05-21 23:17 ` [PATCH v13 22/22] KVM: selftests: Add TDX lifecycle test Lisa Wang
2026-06-16 17:51 ` [PATCH v13 00/22] TDX KVM selftests Ackerley Tng
2026-06-16 18:48 ` Sean Christopherson
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=f8937d16-4aed-44d9-a058-beff56eac4ad@intel.com \
--to=xiaoyao.li@intel.com \
--cc=ackerleytng@google.com \
--cc=afranji@google.com \
--cc=ajones@ventanamicro.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=erdemaktas@google.com \
--cc=ira.weiny@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=jmcrey@google.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pratikrajesh.sampat@amd.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=runanwang@google.com \
--cc=sagis@google.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=wyihan@google.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.