Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 30.11.23 08:37, Xiaoyao Li wrote:
On 11/20/2023 5:24 PM, David Hildenbrand wrote:
uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
{
uint8_t mask = mr->dirty_log_mask;
diff --git a/system/physmem.c b/system/physmem.c
index fc2b0fee0188..0af2213cbd9c 100644
--- a/system/physmem.c
+++ b/system/physmem.c
@@ -1841,6 +1841,20 @@ static void ram_block_add(RAMBlock *new_block,
Error **errp)
}
}
+#ifdef CONFIG_KVM
+ if (kvm_enabled() && new_block->flags & RAM_GUEST_MEMFD &&
I recall that we prefer to write this as
if (kvm_enabled() && (new_block->flags & RAM_GUEST_MEMFD) &&
get it.
Thanks!
+ new_block->guest_memfd < 0) {
+ /* TODO: to decide if KVM_GUEST_MEMFD_ALLOW_HUGEPAGE is
supported */
+ uint64_t flags = 0;
+ new_block->guest_memfd =
kvm_create_guest_memfd(new_block->max_length,
+ flags, errp);
Get rid of "flags" and just pass 0". Whatever code wants to pass flags
later can decide how to do that.
How to handle it please see the reply to patch 3.
If patch #3 cannot go in now and has to be deferred, then please clean
this here up. Otherwise, as suggested, squash with #3.
Depending on KVM_GUEST_MEMFD_ALLOW_HUGEPAGE support :)
--
Cheers,
David / dhildenb
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 11/18/2023 4:35 AM, Isaku Yamahata wrote:
On Wed, Nov 15, 2023 at 02:14:11AM -0500,
Xiaoyao Li wrote:
diff --git a/system/physmem.c b/system/physmem.c
index fc2b0fee0188..0af2213cbd9c 100644
--- a/system/physmem.c
+++ b/system/physmem.c
@@ -1841,6 +1841,20 @@ static void ram_block_add(RAMBlock *new_block, Error
**errp)
}
}
+#ifdef CONFIG_KVM
+if (kvm_enabled() && new_block->flags & RAM_GUEST_MEMFD &&
+new_block->guest_memfd < 0) {
+/* TODO: to decide if KVM_GUEST_MEMFD_ALLOW_HUGEPAGE is supported */
+uint64_t flags = 0;
+new_block->guest_memfd = kvm_create_guest_memfd(new_block->max_length,
+flags, errp);
+if (new_block->guest_memfd < 0) {
+qemu_mutex_unlock_ramlist();
+return;
+}
+}
+#endif
+
We should define kvm_create_guest_memfd() stub in accel/stub/kvm-stub.c.
We can remove this #ifdef.
Nice suggestion! Will use stub.
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 11/20/2023 5:24 PM, David Hildenbrand wrote:
uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
{
uint8_t mask = mr->dirty_log_mask;
diff --git a/system/physmem.c b/system/physmem.c
index fc2b0fee0188..0af2213cbd9c 100644
--- a/system/physmem.c
+++ b/system/physmem.c
@@ -1841,6 +1841,20 @@ static void ram_block_add(RAMBlock *new_block,
Error **errp)
}
}
+#ifdef CONFIG_KVM
+ if (kvm_enabled() && new_block->flags & RAM_GUEST_MEMFD &&
I recall that we prefer to write this as
if (kvm_enabled() && (new_block->flags & RAM_GUEST_MEMFD) &&
get it.
Thanks!
+ new_block->guest_memfd < 0) {
+ /* TODO: to decide if KVM_GUEST_MEMFD_ALLOW_HUGEPAGE is
supported */
+ uint64_t flags = 0;
+ new_block->guest_memfd =
kvm_create_guest_memfd(new_block->max_length,
+ flags, errp);
Get rid of "flags" and just pass 0". Whatever code wants to pass flags
later can decide how to do that.
How to handle it please see the reply to patch 3.
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 11/20/2023 5:19 PM, David Hildenbrand wrote: On 16.11.23 03:45, Xiaoyao Li wrote: On 11/16/2023 1:54 AM, David Hildenbrand wrote: On 15.11.23 08:14, Xiaoyao Li wrote: Add KVM guest_memfd support to RAMBlock so both normal hva based memory and kvm guest memfd based private memory can be associated in one RAMBlock. Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to create private guest_memfd during RAMBlock setup. Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of confidential guests, such as TDX VM. How and when to set it for memory backends will be implemented in the following patches. Can you elaborate (and add to the patch description if there is good reason) why we need that flag and why we cannot simply rely on the VM type instead to decide whether to allocate a guest_memfd or not? The reason is, relying on the VM type is sort of hack that we need to get the MachineState instance and retrieve the vm type info. I think it's better not to couple them. More importantly, it's not flexible and extensible for future case that not all the memory need guest memfd. Okay. In that case, please update the documentation of all functions where we are allowed to pass in RAM_GUEST_MEMFD. There are a couple of them in include/exec/memory.h sure, thanks! I'll note that the name/terminology of "RAM_GUEST_MEMFD" is extremely Linux+kvm specific. But I cannot really come up with something better right now.
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
{
uint8_t mask = mr->dirty_log_mask;
diff --git a/system/physmem.c b/system/physmem.c
index fc2b0fee0188..0af2213cbd9c 100644
--- a/system/physmem.c
+++ b/system/physmem.c
@@ -1841,6 +1841,20 @@ static void ram_block_add(RAMBlock *new_block, Error
**errp)
}
}
+#ifdef CONFIG_KVM
+if (kvm_enabled() && new_block->flags & RAM_GUEST_MEMFD &&
I recall that we prefer to write this as
if (kvm_enabled() && (new_block->flags & RAM_GUEST_MEMFD) &&
+new_block->guest_memfd < 0) {
+/* TODO: to decide if KVM_GUEST_MEMFD_ALLOW_HUGEPAGE is supported */
+uint64_t flags = 0;
+new_block->guest_memfd = kvm_create_guest_memfd(new_block->max_length,
+flags, errp);
Get rid of "flags" and just pass 0". Whatever code wants to pass flags
later can decide how to do that.
--
Cheers,
David / dhildenb
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 16.11.23 03:45, Xiaoyao Li wrote: On 11/16/2023 1:54 AM, David Hildenbrand wrote: On 15.11.23 08:14, Xiaoyao Li wrote: Add KVM guest_memfd support to RAMBlock so both normal hva based memory and kvm guest memfd based private memory can be associated in one RAMBlock. Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to create private guest_memfd during RAMBlock setup. Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of confidential guests, such as TDX VM. How and when to set it for memory backends will be implemented in the following patches. Can you elaborate (and add to the patch description if there is good reason) why we need that flag and why we cannot simply rely on the VM type instead to decide whether to allocate a guest_memfd or not? The reason is, relying on the VM type is sort of hack that we need to get the MachineState instance and retrieve the vm type info. I think it's better not to couple them. More importantly, it's not flexible and extensible for future case that not all the memory need guest memfd. Okay. In that case, please update the documentation of all functions where we are allowed to pass in RAM_GUEST_MEMFD. There are a couple of them in include/exec/memory.h I'll note that the name/terminology of "RAM_GUEST_MEMFD" is extremely Linux+kvm specific. But I cannot really come up with something better right now. -- Cheers, David / dhildenb
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On Wed, Nov 15, 2023 at 02:14:11AM -0500,
Xiaoyao Li wrote:
> diff --git a/system/physmem.c b/system/physmem.c
> index fc2b0fee0188..0af2213cbd9c 100644
> --- a/system/physmem.c
> +++ b/system/physmem.c
> @@ -1841,6 +1841,20 @@ static void ram_block_add(RAMBlock *new_block, Error
> **errp)
> }
> }
>
> +#ifdef CONFIG_KVM
> +if (kvm_enabled() && new_block->flags & RAM_GUEST_MEMFD &&
> +new_block->guest_memfd < 0) {
> +/* TODO: to decide if KVM_GUEST_MEMFD_ALLOW_HUGEPAGE is supported */
> +uint64_t flags = 0;
> +new_block->guest_memfd =
> kvm_create_guest_memfd(new_block->max_length,
> +flags, errp);
> +if (new_block->guest_memfd < 0) {
> +qemu_mutex_unlock_ramlist();
> +return;
> +}
> +}
> +#endif
> +
We should define kvm_create_guest_memfd() stub in accel/stub/kvm-stub.c.
We can remove this #ifdef.
--
Isaku Yamahata
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 11/15/2023 6:20 PM, Daniel P. Berrangé wrote:
On Wed, Nov 15, 2023 at 02:14:11AM -0500, Xiaoyao Li wrote:
Add KVM guest_memfd support to RAMBlock so both normal hva based memory
and kvm guest memfd based private memory can be associated in one RAMBlock.
Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to
create private guest_memfd during RAMBlock setup.
Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of
confidential guests, such as TDX VM. How and when to set it for memory
backends will be implemented in the following patches.
Introduce memory_region_has_guest_memfd() to query if the MemoryRegion has
KVM guest_memfd allocated.
Signed-off-by: Xiaoyao Li
---
Changes in v3:
- rename gmem to guest_memfd;
- close(guest_memfd) when RAMBlock is released; (Daniel P. Berrangé)
- Suqash the patch that introduces memory_region_has_guest_memfd().
---
accel/kvm/kvm-all.c | 24
include/exec/memory.h | 13 +
include/exec/ramblock.h | 1 +
include/sysemu/kvm.h| 2 ++
system/memory.c | 5 +
system/physmem.c| 27 ---
6 files changed, 69 insertions(+), 3 deletions(-)
diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index c1b40e873531..9f751d4971f8 100644
--- a/accel/kvm/kvm-all.c
+++ b/accel/kvm/kvm-all.c
@@ -101,6 +101,7 @@ bool kvm_msi_use_devid;
bool kvm_has_guest_debug;
static int kvm_sstep_flags;
static bool kvm_immediate_exit;
+static bool kvm_guest_memfd_supported;
static hwaddr kvm_max_slot_size = ~0;
static const KVMCapabilityInfo kvm_required_capabilites[] = {
@@ -2397,6 +2398,8 @@ static int kvm_init(MachineState *ms)
}
s->as = g_new0(struct KVMAs, s->nr_as);
+kvm_guest_memfd_supported = kvm_check_extension(s, KVM_CAP_GUEST_MEMFD);
+
if (object_property_find(OBJECT(current_machine), "kvm-type")) {
g_autofree char *kvm_type =
object_property_get_str(OBJECT(current_machine),
"kvm-type",
@@ -4078,3 +4081,24 @@ void query_stats_schemas_cb(StatsSchemaList **result,
Error **errp)
query_stats_schema_vcpu(first_cpu, _args);
}
}
+
+int kvm_create_guest_memfd(uint64_t size, uint64_t flags, Error **errp)
+{
+int fd;
+struct kvm_create_guest_memfd guest_memfd = {
+.size = size,
+.flags = flags,
+};
+
+if (!kvm_guest_memfd_supported) {
+error_setg(errp, "KVM doesn't support guest memfd\n");
+return -EOPNOTSUPP;
Returning an errno value is unusual when we have an 'Error **errp' parameter
for reporting, and the following codepath merely returns -1, so this is
inconsistent. Just return -1 here too.
OK.
+}
+
+fd = kvm_vm_ioctl(kvm_state, KVM_CREATE_GUEST_MEMFD, _memfd);
+if (fd < 0) {
+error_setg_errno(errp, errno, "%s: error creating kvm guest memfd\n",
__func__);
I'd prefer an explicit 'return -1' here, even though 'fd' is technically going
to be -1 already.
Also including __func__ in the error message is not really needed IMHO
OK
+}
+
+return fd;
+}
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 831f7c996d9d..f780367ab1bd 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -243,6 +243,9 @@ typedef struct IOMMUTLBEvent {
/* RAM FD is opened read-only */
#define RAM_READONLY_FD (1 << 11)
+/* RAM can be private that has kvm gmem backend */
+#define RAM_GUEST_MEMFD (1 << 12)
+
static inline void iommu_notifier_init(IOMMUNotifier *n, IOMMUNotify fn,
IOMMUNotifierFlag flags,
hwaddr start, hwaddr end,
@@ -1702,6 +1705,16 @@ static inline bool memory_region_is_romd(MemoryRegion
*mr)
*/
bool memory_region_is_protected(MemoryRegion *mr);
+/**
+ * memory_region_has_guest_memfd: check whether a memory region has guest_memfd
+ * associated
+ *
+ * Returns %true if a memory region's ram_block has valid guest_memfd assigned.
+ *
+ * @mr: the memory region being queried
+ */
+bool memory_region_has_guest_memfd(MemoryRegion *mr);
+
/**
* memory_region_get_iommu: check whether a memory region is an iommu
*
diff --git a/include/exec/ramblock.h b/include/exec/ramblock.h
index 69c6a5390293..0a17ba882729 100644
--- a/include/exec/ramblock.h
+++ b/include/exec/ramblock.h
@@ -41,6 +41,7 @@ struct RAMBlock {
QLIST_HEAD(, RAMBlockNotifier) ramblock_notifiers;
int fd;
uint64_t fd_offset;
+int guest_memfd;
size_t page_size;
/* dirty bitmap used during migration */
unsigned long *bmap;
diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
index d61487816421..fedc28c7d17f 100644
--- a/include/sysemu/kvm.h
+++ b/include/sysemu/kvm.h
@@ -538,4 +538,6 @@ bool kvm_arch_cpu_check_are_resettable(void);
bool kvm_dirty_ring_enabled(void);
uint32_t kvm_dirty_ring_size(void);
+
+int
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 11/16/2023 1:54 AM, David Hildenbrand wrote: On 15.11.23 08:14, Xiaoyao Li wrote: Add KVM guest_memfd support to RAMBlock so both normal hva based memory and kvm guest memfd based private memory can be associated in one RAMBlock. Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to create private guest_memfd during RAMBlock setup. Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of confidential guests, such as TDX VM. How and when to set it for memory backends will be implemented in the following patches. Can you elaborate (and add to the patch description if there is good reason) why we need that flag and why we cannot simply rely on the VM type instead to decide whether to allocate a guest_memfd or not? The reason is, relying on the VM type is sort of hack that we need to get the MachineState instance and retrieve the vm type info. I think it's better not to couple them. More importantly, it's not flexible and extensible for future case that not all the memory need guest memfd.
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On 15.11.23 08:14, Xiaoyao Li wrote: Add KVM guest_memfd support to RAMBlock so both normal hva based memory and kvm guest memfd based private memory can be associated in one RAMBlock. Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to create private guest_memfd during RAMBlock setup. Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of confidential guests, such as TDX VM. How and when to set it for memory backends will be implemented in the following patches. Can you elaborate (and add to the patch description if there is good reason) why we need that flag and why we cannot simply rely on the VM type instead to decide whether to allocate a guest_memfd or not? -- Cheers, David / dhildenb
Re: [PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
On Wed, Nov 15, 2023 at 02:14:11AM -0500, Xiaoyao Li wrote:
> Add KVM guest_memfd support to RAMBlock so both normal hva based memory
> and kvm guest memfd based private memory can be associated in one RAMBlock.
>
> Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to
> create private guest_memfd during RAMBlock setup.
>
> Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of
> confidential guests, such as TDX VM. How and when to set it for memory
> backends will be implemented in the following patches.
>
> Introduce memory_region_has_guest_memfd() to query if the MemoryRegion has
> KVM guest_memfd allocated.
>
> Signed-off-by: Xiaoyao Li
> ---
> Changes in v3:
> - rename gmem to guest_memfd;
> - close(guest_memfd) when RAMBlock is released; (Daniel P. Berrangé)
> - Suqash the patch that introduces memory_region_has_guest_memfd().
> ---
> accel/kvm/kvm-all.c | 24
> include/exec/memory.h | 13 +
> include/exec/ramblock.h | 1 +
> include/sysemu/kvm.h| 2 ++
> system/memory.c | 5 +
> system/physmem.c| 27 ---
> 6 files changed, 69 insertions(+), 3 deletions(-)
>
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index c1b40e873531..9f751d4971f8 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -101,6 +101,7 @@ bool kvm_msi_use_devid;
> bool kvm_has_guest_debug;
> static int kvm_sstep_flags;
> static bool kvm_immediate_exit;
> +static bool kvm_guest_memfd_supported;
> static hwaddr kvm_max_slot_size = ~0;
>
> static const KVMCapabilityInfo kvm_required_capabilites[] = {
> @@ -2397,6 +2398,8 @@ static int kvm_init(MachineState *ms)
> }
> s->as = g_new0(struct KVMAs, s->nr_as);
>
> +kvm_guest_memfd_supported = kvm_check_extension(s, KVM_CAP_GUEST_MEMFD);
> +
> if (object_property_find(OBJECT(current_machine), "kvm-type")) {
> g_autofree char *kvm_type =
> object_property_get_str(OBJECT(current_machine),
> "kvm-type",
> @@ -4078,3 +4081,24 @@ void query_stats_schemas_cb(StatsSchemaList **result,
> Error **errp)
> query_stats_schema_vcpu(first_cpu, _args);
> }
> }
> +
> +int kvm_create_guest_memfd(uint64_t size, uint64_t flags, Error **errp)
> +{
> +int fd;
> +struct kvm_create_guest_memfd guest_memfd = {
> +.size = size,
> +.flags = flags,
> +};
> +
> +if (!kvm_guest_memfd_supported) {
> +error_setg(errp, "KVM doesn't support guest memfd\n");
> +return -EOPNOTSUPP;
Returning an errno value is unusual when we have an 'Error **errp' parameter
for reporting, and the following codepath merely returns -1, so this is
inconsistent. Just return -1 here too.
> +}
> +
> +fd = kvm_vm_ioctl(kvm_state, KVM_CREATE_GUEST_MEMFD, _memfd);
> +if (fd < 0) {
> +error_setg_errno(errp, errno, "%s: error creating kvm guest
> memfd\n", __func__);
I'd prefer an explicit 'return -1' here, even though 'fd' is technically going
to be -1 already.
Also including __func__ in the error message is not really needed IMHO
> +}
> +
> +return fd;
> +}
> diff --git a/include/exec/memory.h b/include/exec/memory.h
> index 831f7c996d9d..f780367ab1bd 100644
> --- a/include/exec/memory.h
> +++ b/include/exec/memory.h
> @@ -243,6 +243,9 @@ typedef struct IOMMUTLBEvent {
> /* RAM FD is opened read-only */
> #define RAM_READONLY_FD (1 << 11)
>
> +/* RAM can be private that has kvm gmem backend */
> +#define RAM_GUEST_MEMFD (1 << 12)
> +
> static inline void iommu_notifier_init(IOMMUNotifier *n, IOMMUNotify fn,
> IOMMUNotifierFlag flags,
> hwaddr start, hwaddr end,
> @@ -1702,6 +1705,16 @@ static inline bool memory_region_is_romd(MemoryRegion
> *mr)
> */
> bool memory_region_is_protected(MemoryRegion *mr);
>
> +/**
> + * memory_region_has_guest_memfd: check whether a memory region has
> guest_memfd
> + * associated
> + *
> + * Returns %true if a memory region's ram_block has valid guest_memfd
> assigned.
> + *
> + * @mr: the memory region being queried
> + */
> +bool memory_region_has_guest_memfd(MemoryRegion *mr);
> +
> /**
> * memory_region_get_iommu: check whether a memory region is an iommu
> *
> diff --git a/include/exec/ramblock.h b/include/exec/ramblock.h
> index 69c6a5390293..0a17ba882729 100644
> --- a/include/exec/ramblock.h
> +++ b/include/exec/ramblock.h
> @@ -41,6 +41,7 @@ struct RAMBlock {
> QLIST_HEAD(, RAMBlockNotifier) ramblock_notifiers;
> int fd;
> uint64_t fd_offset;
> +int guest_memfd;
> size_t page_size;
> /* dirty bitmap used during migration */
> unsigned long *bmap;
> diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> index d61487816421..fedc28c7d17f 100644
> --- a/include/sysemu/kvm.h
> +++ b/include/sysemu/kvm.h
> @@ -538,4 +538,6 @@
[PATCH v3 02/70] RAMBlock: Add support of KVM private guest memfd
Add KVM guest_memfd support to RAMBlock so both normal hva based memory
and kvm guest memfd based private memory can be associated in one RAMBlock.
Introduce new flag RAM_GUEST_MEMFD. When it's set, it calls KVM ioctl to
create private guest_memfd during RAMBlock setup.
Note, RAM_GUEST_MEMFD is supposed to be set for memory backends of
confidential guests, such as TDX VM. How and when to set it for memory
backends will be implemented in the following patches.
Introduce memory_region_has_guest_memfd() to query if the MemoryRegion has
KVM guest_memfd allocated.
Signed-off-by: Xiaoyao Li
---
Changes in v3:
- rename gmem to guest_memfd;
- close(guest_memfd) when RAMBlock is released; (Daniel P. Berrangé)
- Suqash the patch that introduces memory_region_has_guest_memfd().
---
accel/kvm/kvm-all.c | 24
include/exec/memory.h | 13 +
include/exec/ramblock.h | 1 +
include/sysemu/kvm.h| 2 ++
system/memory.c | 5 +
system/physmem.c| 27 ---
6 files changed, 69 insertions(+), 3 deletions(-)
diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index c1b40e873531..9f751d4971f8 100644
--- a/accel/kvm/kvm-all.c
+++ b/accel/kvm/kvm-all.c
@@ -101,6 +101,7 @@ bool kvm_msi_use_devid;
bool kvm_has_guest_debug;
static int kvm_sstep_flags;
static bool kvm_immediate_exit;
+static bool kvm_guest_memfd_supported;
static hwaddr kvm_max_slot_size = ~0;
static const KVMCapabilityInfo kvm_required_capabilites[] = {
@@ -2397,6 +2398,8 @@ static int kvm_init(MachineState *ms)
}
s->as = g_new0(struct KVMAs, s->nr_as);
+kvm_guest_memfd_supported = kvm_check_extension(s, KVM_CAP_GUEST_MEMFD);
+
if (object_property_find(OBJECT(current_machine), "kvm-type")) {
g_autofree char *kvm_type =
object_property_get_str(OBJECT(current_machine),
"kvm-type",
@@ -4078,3 +4081,24 @@ void query_stats_schemas_cb(StatsSchemaList **result,
Error **errp)
query_stats_schema_vcpu(first_cpu, _args);
}
}
+
+int kvm_create_guest_memfd(uint64_t size, uint64_t flags, Error **errp)
+{
+int fd;
+struct kvm_create_guest_memfd guest_memfd = {
+.size = size,
+.flags = flags,
+};
+
+if (!kvm_guest_memfd_supported) {
+error_setg(errp, "KVM doesn't support guest memfd\n");
+return -EOPNOTSUPP;
+}
+
+fd = kvm_vm_ioctl(kvm_state, KVM_CREATE_GUEST_MEMFD, _memfd);
+if (fd < 0) {
+error_setg_errno(errp, errno, "%s: error creating kvm guest memfd\n",
__func__);
+}
+
+return fd;
+}
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 831f7c996d9d..f780367ab1bd 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -243,6 +243,9 @@ typedef struct IOMMUTLBEvent {
/* RAM FD is opened read-only */
#define RAM_READONLY_FD (1 << 11)
+/* RAM can be private that has kvm gmem backend */
+#define RAM_GUEST_MEMFD (1 << 12)
+
static inline void iommu_notifier_init(IOMMUNotifier *n, IOMMUNotify fn,
IOMMUNotifierFlag flags,
hwaddr start, hwaddr end,
@@ -1702,6 +1705,16 @@ static inline bool memory_region_is_romd(MemoryRegion
*mr)
*/
bool memory_region_is_protected(MemoryRegion *mr);
+/**
+ * memory_region_has_guest_memfd: check whether a memory region has guest_memfd
+ * associated
+ *
+ * Returns %true if a memory region's ram_block has valid guest_memfd assigned.
+ *
+ * @mr: the memory region being queried
+ */
+bool memory_region_has_guest_memfd(MemoryRegion *mr);
+
/**
* memory_region_get_iommu: check whether a memory region is an iommu
*
diff --git a/include/exec/ramblock.h b/include/exec/ramblock.h
index 69c6a5390293..0a17ba882729 100644
--- a/include/exec/ramblock.h
+++ b/include/exec/ramblock.h
@@ -41,6 +41,7 @@ struct RAMBlock {
QLIST_HEAD(, RAMBlockNotifier) ramblock_notifiers;
int fd;
uint64_t fd_offset;
+int guest_memfd;
size_t page_size;
/* dirty bitmap used during migration */
unsigned long *bmap;
diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
index d61487816421..fedc28c7d17f 100644
--- a/include/sysemu/kvm.h
+++ b/include/sysemu/kvm.h
@@ -538,4 +538,6 @@ bool kvm_arch_cpu_check_are_resettable(void);
bool kvm_dirty_ring_enabled(void);
uint32_t kvm_dirty_ring_size(void);
+
+int kvm_create_guest_memfd(uint64_t size, uint64_t flags, Error **errp);
#endif
diff --git a/system/memory.c b/system/memory.c
index 304fa843ea12..69741d91bbb7 100644
--- a/system/memory.c
+++ b/system/memory.c
@@ -1862,6 +1862,11 @@ bool memory_region_is_protected(MemoryRegion *mr)
return mr->ram && (mr->ram_block->flags & RAM_PROTECTED);
}
+bool memory_region_has_guest_memfd(MemoryRegion *mr)
+{
+return mr->ram_block && mr->ram_block->guest_memfd >= 0;
+}
+
uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
{
uint8_t
