You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the mmap support patch series to v17, and update the direct map
removal series to apply on top of v17. Rebase all the other series.
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Copy file name to clipboardExpand all lines: resources/hiding_ci/linux_patches/05-mmap-support/0001-KVM-Rename-CONFIG_KVM_PRIVATE_MEM-to-CONFIG_KVM_GUES.patch
+45-42Lines changed: 45 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -1,27 +1,30 @@
1
-
From 000264f8823f76fb6cf91dc40ace84a29a0fa089 Mon Sep 17 00:00:00 2001
1
+
From 83ed02c1c583b5b831e7827453845fe4fd7b4c80 Mon Sep 17 00:00:00 2001
2
2
From: Fuad Tabba <tabba@google.com>
3
-
Date: Tue, 15 Jul 2025 10:33:30 +0100
4
-
Subject: [PATCH 01/46] KVM: Rename CONFIG_KVM_PRIVATE_MEM to CONFIG_KVM_GMEM
3
+
Date: Tue, 29 Jul 2025 15:54:32 -0700
4
+
Subject: [PATCH 01/49] KVM: Rename CONFIG_KVM_PRIVATE_MEM to
5
+
CONFIG_KVM_GUEST_MEMFD
5
6
6
-
Rename the Kconfig option CONFIG_KVM_PRIVATE_MEM to CONFIG_KVM_GMEM. The
7
-
original name implied that the feature only supported "private" memory.
8
-
However, CONFIG_KVM_PRIVATE_MEM enables guest_memfd in general, which is
9
-
not exclusively for private memory. Subsequent patches in this series
10
-
will add guest_memfd support for non-CoCo VMs, whose memory is not
11
-
private.
7
+
Rename the Kconfig option CONFIG_KVM_PRIVATE_MEM to
8
+
CONFIG_KVM_GUEST_MEMFD. The original name implied that the feature only
9
+
supported "private" memory. However, CONFIG_KVM_PRIVATE_MEM enables
10
+
guest_memfd in general, which is not exclusively for private memory.
11
+
Subsequent patches in this series will add guest_memfd support for
12
+
non-CoCo VMs, whose memory is not private.
12
13
13
-
Renaming the Kconfig option to CONFIG_KVM_GMEM more accurately reflects
14
-
its broader scope as the main Kconfig option for all guest_memfd-backed
15
-
memory. This provides clearer semantics for the option and avoids
16
-
confusion as new features are introduced.
14
+
Renaming the Kconfig option to CONFIG_KVM_GUEST_MEMFD more accurately
15
+
reflects its broader scope as the main Kconfig option for all
16
+
guest_memfd-backed memory. This provides clearer semantics for the
17
+
option and avoids confusion as new features are introduced.
17
18
18
19
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
19
20
Reviewed-by: Gavin Shan <gshan@redhat.com>
20
21
Reviewed-by: Shivank Garg <shivankg@amd.com>
21
22
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
23
+
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
22
24
Co-developed-by: David Hildenbrand <david@redhat.com>
23
25
Signed-off-by: David Hildenbrand <david@redhat.com>
24
26
Signed-off-by: Fuad Tabba <tabba@google.com>
27
+
Signed-off-by: Sean Christopherson <seanjc@google.com>
Copy file name to clipboardExpand all lines: resources/hiding_ci/linux_patches/05-mmap-support/0002-KVM-Rename-CONFIG_KVM_GENERIC_PRIVATE_MEM-to-CONFIG_.patch
0 commit comments