On 8/31/26 02:25, Ackerley Tng via B4 Relay wrote:
From: Sean Christopherson <seanjc@google.com>
Use kvm_mem_is_private() when populating guest_memfd instead of using an
open coded equivalent. In addition to simplifying the populate code *now*,
this avoids the need to provide a range-based gmem lookup API in the future
as well.
No functional change intended.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Suggested-by: Xiaoyao Li <redacted>
Reviewed-by: Xiaoyao Li <redacted>
Reviewed-by: Binbin Wu <redacted>
Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev>
Signed-off-by: Ackerley Tng <redacted>
---
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David